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>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2 0/2] Convert FSMC NAND controller driver to ->exec_op()
Date: Sun, 18 Feb 2018 08:59:18 +0100 [thread overview]
Message-ID: <20180218085918.74a579b8@bbrezillon> (raw)
In-Reply-To: <20180216142248.32345-1-miquel.raynal@bootlin.com>
On Fri, 16 Feb 2018 15:22:46 +0100
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> Hello,
>
> Now that the ->exec_op() interface has been merged in the NAND core,
> convert the FSMC NAND controller driver to it.
>
> A previous step involves getting rid of ->IO_ADDR_[R|W] across the
> driver, which is almost entirely done in the first patch. Because the
> driver still uses at that point the default implementations of
> ->read/write_byte/word(), some references are still present but are
> removed as soon as the driver is moved to ->exec_op(), when this
> dependency disappears.
>
> Best regards,
> Miquèl
>
>
> Changes since v1:
> =================
>
> - Forgot about the NAND unique ID for now, this will need a deeper
> rework of the MTD stack and is very (ONFI-)NAND-specific.
> - Split the migration of FSMC driver to ->exec_op() into two patches,
> one to get rid of ->IO_ADDR_[R|W], the other to implement ->exec_op()
> and ->select_chip() which is also needed.
> - Got rid of the additional ->regs entry in the FSMC structure, using
> the existing entry ->regs_va instead.
>
>
> Miquel Raynal (2):
> mtd: nand: fsmc: get rid of IO_ADDR_[R|W]
> mtd: nand: fsmc: use ->exec_op()
Applied.
Thanks,
Boris
>
> drivers/mtd/nand/fsmc_nand.c | 242 ++++++++++++++++++++++++-------------------
> 1 file changed, 137 insertions(+), 105 deletions(-)
>
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-02-18 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 14:22 [PATCH v2 0/2] Convert FSMC NAND controller driver to ->exec_op() Miquel Raynal
2018-02-16 14:22 ` [PATCH v2 1/2] mtd: nand: fsmc: get rid of IO_ADDR_[R|W] Miquel Raynal
2018-02-16 14:22 ` [PATCH v2 2/2] mtd: nand: fsmc: use ->exec_op() Miquel Raynal
2018-02-18 7:59 ` 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=20180218085918.74a579b8@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--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