From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>,
Brian Norris <computersforpeace@gmail.com>,
kernel@pengutronix.de
Subject: Re: [PATCH 2/3] mtd: nand: mxc: Add own write_page
Date: Mon, 18 Dec 2017 22:00:54 +0100 [thread overview]
Message-ID: <20171218220043.427f59ed@bbrezillon> (raw)
In-Reply-To: <20171218204935.cmacd6bsvhl7y277@pengutronix.de>
On Mon, 18 Dec 2017 21:49:35 +0100
Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Mon, Dec 18, 2017 at 06:03:08PM +0100, Boris Brezillon wrote:
> > On Fri, 15 Dec 2017 09:55:03 +0100
> > Sascha Hauer <s.hauer@pengutronix.de> wrote:
> >
> > > Now that we have our own read_page function add a write_page function
> > > for consistency aswell. This can be a lot easier than the generic
> > > function since we do not have to iterate over subpages but can write
> > > the whole page at once.
> > >
> > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > > ---
> > > drivers/mtd/nand/mxc_nand.c | 17 +++++++++++++++++
> > > 1 file changed, 17 insertions(+)
> > >
> > > diff --git a/drivers/mtd/nand/mxc_nand.c b/drivers/mtd/nand/mxc_nand.c
> > > index 65d5cde4692b..a54804f14bb1 100644
> > > --- a/drivers/mtd/nand/mxc_nand.c
> > > +++ b/drivers/mtd/nand/mxc_nand.c
> > > @@ -142,6 +142,8 @@ struct mxc_nand_devtype_data {
> > > void (*preset)(struct mtd_info *);
> > > int (*read_page)(struct mtd_info *mtd, struct nand_chip *chip,
> > > uint8_t *buf, int oob_required, int page);
> > > + int (*write_page)(struct mtd_info *mtd, struct nand_chip *chip,
> > > + const uint8_t *buf, int oob_required, int page);
> > > void (*send_cmd)(struct mxc_nand_host *, uint16_t, int);
> > > void (*send_addr)(struct mxc_nand_host *, uint16_t, int);
> > > void (*send_page)(struct mtd_info *, unsigned int);
> > > @@ -658,6 +660,17 @@ static int mxc_nand_read_page_hwecc_v2_v3(struct mtd_info *mtd,
> > > return max_bitflips;
> > > }
> > >
> > > +static int mxc_nand_write_page_hwecc_v2_v3(struct mtd_info *mtd,
> > > + struct nand_chip *chip,
> > > + const uint8_t *buf, int oob_required,
> > > + int page)
> > > +{
> > > + chip->write_buf(mtd, buf, mtd->writesize);
> > > + chip->write_buf(mtd, chip->oob_poi, mtd->oobsize);
> > > +
> > > + return 0;
> > > +}
> > > +
> > > static int mxc_nand_calculate_ecc(struct mtd_info *mtd, const u_char *dat,
> > > u_char *ecc_code)
> > > {
> > > @@ -1456,6 +1469,7 @@ static const struct mxc_nand_devtype_data imx27_nand_devtype_data = {
> > > static const struct mxc_nand_devtype_data imx25_nand_devtype_data = {
> > > .preset = preset_v2,
> > > .read_page = mxc_nand_read_page_hwecc_v2_v3,
> > > + .write_page = mxc_nand_write_page_hwecc_v2_v3,
> > > .send_cmd = send_cmd_v1_v2,
> > > .send_addr = send_addr_v1_v2,
> > > .send_page = send_page_v2,
> > > @@ -1482,6 +1496,7 @@ static const struct mxc_nand_devtype_data imx25_nand_devtype_data = {
> > > static const struct mxc_nand_devtype_data imx51_nand_devtype_data = {
> > > .preset = preset_v3,
> > > .read_page = mxc_nand_read_page_hwecc_v2_v3,
> > > + .write_page = mxc_nand_write_page_hwecc_v2_v3,
> > > .send_cmd = send_cmd_v3,
> > > .send_addr = send_addr_v3,
> > > .send_page = send_page_v3,
> > > @@ -1508,6 +1523,7 @@ static const struct mxc_nand_devtype_data imx51_nand_devtype_data = {
> > > static const struct mxc_nand_devtype_data imx53_nand_devtype_data = {
> > > .preset = preset_v3,
> > > .read_page = mxc_nand_read_page_hwecc_v2_v3,
> > > + .write_page = mxc_nand_write_page_hwecc_v2_v3,
> > > .send_cmd = send_cmd_v3,
> > > .send_addr = send_addr_v3,
> > > .send_page = send_page_v3,
> > > @@ -1766,6 +1782,7 @@ static int mxcnd_probe(struct platform_device *pdev)
> > > switch (this->ecc.mode) {
> > > case NAND_ECC_HW:
> > > this->ecc.read_page = host->devtype_data->read_page;
> > > + this->ecc.write_page = host->devtype_data->write_page;
> > > this->ecc.calculate = mxc_nand_calculate_ecc;
> >
> > I'm pretty sure you don't need this dummy calculate method now that you
> > provide your own ->write/read_page() implementations.
>
> True for the v2/v3 type controllers, but not for v1 which I haven't
> changed in this series.
Indeed, forgot that v1 support was not updated.
>
> Will update the series next year.
Thanks.
>
> Thanks
> Sascha
>
next prev parent reply other threads:[~2017-12-18 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 8:55 mtd: nand: mxc: Fix failed/corrected values Sascha Hauer
2017-12-15 8:55 ` [PATCH 1/3] " Sascha Hauer
2017-12-18 16:52 ` Boris Brezillon
2017-12-15 8:55 ` [PATCH 2/3] mtd: nand: mxc: Add own write_page Sascha Hauer
2017-12-18 16:59 ` Boris Brezillon
2017-12-18 17:03 ` Boris Brezillon
2017-12-18 20:49 ` Sascha Hauer
2017-12-18 21:00 ` Boris Brezillon [this message]
2017-12-15 8:55 ` [PATCH 3/3] mtd: nand: mxc: Drop now unnecessary correct_data function Sascha Hauer
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=20171218220043.427f59ed@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=s.hauer@pengutronix.de \
/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.