From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/2] Uniform way to pass a NAND ID table to the core
Date: Tue, 27 Mar 2018 09:17:37 +0200 [thread overview]
Message-ID: <20180327091737.7d09b189@bbrezillon> (raw)
In-Reply-To: <20180321131235.9822-1-miquel.raynal@bootlin.com>
Hi Miquel,
On Wed, 21 Mar 2018 14:12:33 +0100
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> Hello,
>
> As part of the work of migrating all the drivers to nand_scan(), and
> because nand_scan() does not provide a way to pass any ID table, create
> a field in NAND chip so a controller driver can expose its ID table to
> the core through it and stop using the last parameter of
> nand_scan_ident() for that.
I'm not a big fan of adding yet another field to the nand_chip struct.
Could we instead create a nand_scan_with_ids() function that takes an
extra ID table in argument and then make nand_scan() a wrapper around
this new function?
int nand_scan_with_ids(struct mtd_info *mtd, int max_chips,
struct nand_flash_dev *ids);
static inline int nand_scan(struct mtd_info *mtd, int max_chips)
{
return nand_scan_with_ids(mtd, max_chips, NULL);
}
Regards,
Boris
>
> Apply this to the sm_common driver which is the only one that actually
> provides its own ID table, so there is no remaining driver using this
> third parameter, so all can be moved easily to nand_scan() in a next
> series.
>
> Thanks,
> Miquèl
>
> Miquel Raynal (2):
> mtd: rawnand: add a field in nand_chip to fill an array of IDs
> mtd: rawnand: sm_common: make use of the new flash_ids table entry
>
> drivers/mtd/nand/raw/nand_base.c | 8 ++++++--
> drivers/mtd/nand/raw/sm_common.c | 5 +++--
> include/linux/mtd/rawnand.h | 3 +++
> 3 files changed, 12 insertions(+), 4 deletions(-)
>
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-27 7:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 13:12 [PATCH 0/2] Uniform way to pass a NAND ID table to the core Miquel Raynal
2018-03-21 13:12 ` [PATCH 1/2] mtd: rawnand: add a field in nand_chip to fill an array of IDs Miquel Raynal
2018-03-21 13:12 ` [PATCH 2/2] mtd: rawnand: sm_common: make use of the new flash_ids table entry Miquel Raynal
2018-03-27 7:17 ` Boris Brezillon [this message]
2018-04-21 18:19 ` [PATCH 0/2] Uniform way to pass a NAND ID table to the core Miquel Raynal
2018-04-21 19:28 ` Boris Brezillon
2018-04-22 1:36 ` Miquel Raynal
2018-04-22 5:51 ` Boris Brezillon
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=20180327091737.7d09b189@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
/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