public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Janusz Krzysztofik <jmkrzyszt@gmail.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: linux-omap@vger.kernel.org,
	Boris Brezillon <bbrezillon@kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	Richard Weinberger <richard@nod.at>,
	Aaro Koskinen <aaro.koskinen@iki.fi>,
	linux-kernel@vger.kernel.org, Marek Vasut <marek.vasut@gmail.com>,
	linux-mtd@lists.infradead.org,
	Brian Norris <computersforpeace@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] mtd: rawnand: ams-delta: Drop board specific partition info
Date: Thu, 18 Apr 2019 21:11:14 +0200	[thread overview]
Message-ID: <5022351.qh9aoUC7DE@z50> (raw)
In-Reply-To: <20190418084929.7ac2cb67@xps13>

Hi Miquèl,

I'm wondering if we could register up a custom mtd partition parser from the 
board file.  It could return a pointer to a statically defined table.  Then we 
could add its name to the list of parsers the driver is going to try if the 
board is enabled in .config.
Would that be acceptable from the MTD subsystem point of view?

Thanks,
Janusz


On Thursday, April 18, 2019 8:49:29 AM CEST Miquel Raynal wrote:
> Hi Janusz,
> 
> Janusz Krzysztofik <jmkrzyszt@gmail.com> wrote on Thu, 18 Apr 2019
> 01:09:59 +0200:
> 
> > Hi Aaro, Tony,
> > 
> > On Wednesday, April 17, 2019 11:40:10 AM CEST Miquel Raynal wrote:
> > > Hi Janusz,
> > > 
> > > Janusz Krzysztofik <jmkrzyszt@gmail.com> wrote on Sun, 24 Mar 2019
> > > 23:33:44 +0100:
> > >   
> > > > After recent modifications, only a hardcoded partition info makes
> > > > the driver device specific.  Other than that, the driver uses GPIO
> > > > exclusively and can be used on any hardware.
> > > > 
> > > > Drop the partition info and use MTD partition parser with default list
> > > > of parser names instead.  For the OF parser to work correctly, pass
> > > > device of_node to mtd.
> > > > 
> > > > Amstrad Delta users should append the following partition info to 
their
> > > > kernel command line, possibly by embedding it in CONFIG_CMDLINE:
> > > > 
> > > > mtdparts=ams-delta-nand:3584k(Kernel),256k(u-boot),256k(u-
boot_params),\
> > > > 256k(Amstrad_LDR),27m(File_system),768k(PBL_reserved).
> > > > 
> > > > For their convenience, CONFIG_MTD_CMDLINE_PARTS symbol is selected
> > > > automatically from that board Kconfig if this NAND driver is also
> > > > selected.
> > > > 
> > > > Signed-off-by: Janusz Krzysztofik <jmkrzyszt@gmail.com>
> > > > Cc: Tony Lindgren <tony@atomide.com>
> > > > ---  
> > > 
> > > FYI I am okay with the change but I am waiting for acks before applying
> > > it.  
> > 
> > May we have an ack from you?
> > 
> > If still not convinced with my clarifications, I can add a comment to help 
text 
> > in Kconfig, either squashed or in a follow up patch, on the requirement of 
> > appending mtdparts parameter to command line.  What do you think?
> 
> In the same patch I guess that would be fine.
> 
> Thanks,
> Miquèl
> 





_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-04-18 19:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 22:37 [PATCH] mtd: rawnand: ams-delta: Drop board specific partition info Janusz Krzysztofik
2019-03-20  1:16 ` Aaro Koskinen
2019-03-24 16:48   ` Janusz Krzysztofik
2019-03-24 18:59     ` Aaro Koskinen
2019-03-24 19:24       ` H. Nikolaus Schaller
2019-03-24 20:40         ` Janusz Krzysztofik
2019-03-24 20:30       ` Janusz Krzysztofik
2019-03-24 22:33 ` [PATCH v2] " Janusz Krzysztofik
2019-04-17  9:40   ` Miquel Raynal
2019-04-17 23:09     ` Janusz Krzysztofik
2019-04-18  6:49       ` Miquel Raynal
2019-04-18 19:11         ` Janusz Krzysztofik [this message]
2019-04-24 18:02   ` [PATCH v3] " Janusz Krzysztofik
2019-04-24 22:14     ` Ladislav Michl
2019-04-25 18:42       ` Janusz Krzysztofik
2019-04-27  9:18         ` Ladislav Michl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5022351.qh9aoUC7DE@z50 \
    --to=jmkrzyszt@gmail.com \
    --cc=aaro.koskinen@iki.fi \
    --cc=bbrezillon@kernel.org \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=marek.vasut@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=tony@atomide.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox