From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Boris Brezillon <boris.brezillon@bootlin.com>,
Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>
Cc: linux-mtd@lists.infradead.org, Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [RFC PATCH 0/3] Changes in the internal raw NAND API
Date: Tue, 17 Jul 2018 11:54:51 +0200 [thread overview]
Message-ID: <20180717095454.27935-1-miquel.raynal@bootlin.com> (raw)
Hello,
After having sent two versions of a series removing the
nand_scan_ident/nand_scan_tail limitation that prevents us to allocate
memory at critical moments, we are still discussing the internal API.
To avoid sending again more than 20 patches, this is an RFC of the
internal changes prior to the above modifications in each driver:
1/ Rename struct nand_hw_control -> struct nand_controller which is
much more meaningful.
2/ Rename the function initializing the above structure
nand_hw_control_init() -> nand_controller_init().
3/ Create a nand_controller_ops structure which will be embedded in the
nand_controller structure. These operations are:
int (*attach_chip)(struct nand_chip *) and
void (*detach_chip)(struct nand_chip *).
If we agree on this, I could merge them first and then send the bunch of
patches making use of these API changes.
Thanks,
Miquèl
Miquel Raynal (3):
mtd: rawnand: better name for the controller structure
mtd: rawnand: update the controller structure initialization function
name
mtd: rawnand: add hooks that may be called during nand_scan()
drivers/mtd/nand/raw/atmel/nand-controller.c | 10 +++++-----
drivers/mtd/nand/raw/brcmnand/brcmnand.c | 4 ++--
drivers/mtd/nand/raw/docg4.c | 2 +-
drivers/mtd/nand/raw/fsl_elbc_nand.c | 4 ++--
drivers/mtd/nand/raw/fsl_ifc_nand.c | 4 ++--
drivers/mtd/nand/raw/jz4780_nand.c | 7 ++++---
drivers/mtd/nand/raw/marvell_nand.c | 6 +++---
drivers/mtd/nand/raw/mtk_nand.c | 2 +-
drivers/mtd/nand/raw/nand_base.c | 23 ++++++++++++++++++++---
drivers/mtd/nand/raw/ndfc.c | 4 ++--
drivers/mtd/nand/raw/omap2.c | 2 +-
drivers/mtd/nand/raw/oxnas_nand.c | 4 ++--
drivers/mtd/nand/raw/qcom_nandc.c | 4 ++--
drivers/mtd/nand/raw/s3c2410.c | 4 ++--
drivers/mtd/nand/raw/sunxi_nand.c | 6 +++---
drivers/mtd/nand/raw/tango_nand.c | 4 ++--
drivers/mtd/nand/raw/tegra_nand.c | 6 +++---
drivers/mtd/nand/raw/txx9ndfmc.c | 4 ++--
include/linux/mtd/rawnand.h | 27 ++++++++++++++++++++++-----
19 files changed, 81 insertions(+), 46 deletions(-)
--
2.14.1
next reply other threads:[~2018-07-17 9:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 9:54 Miquel Raynal [this message]
2018-07-17 9:54 ` [RFC PATCH 1/3] mtd: rawnand: better name for the controller structure Miquel Raynal
2018-07-17 11:49 ` Boris Brezillon
2018-07-17 11:58 ` Miquel Raynal
2018-07-17 12:05 ` Boris Brezillon
2018-07-17 9:54 ` [RFC PATCH 2/3] mtd: rawnand: update the controller structure initialization function name Miquel Raynal
2018-07-17 11:51 ` Boris Brezillon
2018-07-17 12:01 ` Miquel Raynal
2018-07-17 9:54 ` [RFC PATCH 3/3] mtd: rawnand: add hooks that may be called during nand_scan() Miquel Raynal
2018-07-17 12:03 ` Boris Brezillon
2018-07-17 12:09 ` Miquel Raynal
2018-07-17 12:13 ` 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=20180717095454.27935-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.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