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: Sun, 22 Apr 2018 07:51:06 +0200 [thread overview]
Message-ID: <20180422075106.76c249a9@bbrezillon> (raw)
In-Reply-To: <20180422033600.014f53c5@xps13>
On Sun, 22 Apr 2018 03:36:00 +0200
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> Hi Boris,
>
> On Sat, 21 Apr 2018 21:28:53 +0200, Boris Brezillon
> <boris.brezillon@bootlin.com> wrote:
>
> > On Sat, 21 Apr 2018 20:19:00 +0200
> > Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> >
> > > Hi Boris,
> > >
> > > On Tue, 27 Mar 2018 09:17:37 +0200, Boris Brezillon
> > > <boris.brezillon@bootlin.com> wrote:
> > >
> > > > 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);
> > > > }
> > >
> > > Sure I can do that, but I found too impacting the fact that we should
> > > patch all the drivers to call nand_scan_with_ids() from your example.
> >
> > Nope we don't have to do that, see the nand_scan() wrapper proposed
> > above.
>
> Actually I was embarrassed by the 'static' keyword, I'll just drop
> it off.
It's "static inline" and that's because I was suggesting to define the
nand_scan() wrapper directly in rawnand.h instead of exporting a symbol
for a one line function.
prev parent reply other threads:[~2018-04-22 5:51 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 ` [PATCH 0/2] Uniform way to pass a NAND ID table to the core Boris Brezillon
2018-04-21 18:19 ` Miquel Raynal
2018-04-21 19:28 ` Boris Brezillon
2018-04-22 1:36 ` Miquel Raynal
2018-04-22 5:51 ` Boris Brezillon [this message]
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=20180422075106.76c249a9@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.