From: Naga Sureshkumar Relli <nagasure@xilinx.com>
To: Boris Brezillon <boris.brezillon@collabora.com>
Cc: "miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"helmut.grohne@intenta.de" <helmut.grohne@intenta.de>,
"richard@nod.at" <richard@nod.at>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"bbrezillon@kernel.org" <bbrezillon@kernel.org>,
"yamada.masahiro@socionext.com" <yamada.masahiro@socionext.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [LINUX PATCH v17 1/2] mtd: rawnand: nand_micron: Do not over write driver's read_page()/write_page()
Date: Wed, 26 Jun 2019 12:12:47 +0000 [thread overview]
Message-ID: <DM6PR02MB4779B5C815FB4DAF33EF4996AFE20@DM6PR02MB4779.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20190626140417.440cf762@collabora.com>
Hi Boris,
> -----Original Message-----
> From: Boris Brezillon <boris.brezillon@collabora.com>
> Sent: Wednesday, June 26, 2019 5:34 PM
> To: Naga Sureshkumar Relli <nagasure@xilinx.com>
> Cc: miquel.raynal@bootlin.com; helmut.grohne@intenta.de; richard@nod.at;
> dwmw2@infradead.org; computersforpeace@gmail.com; marek.vasut@gmail.com;
> vigneshr@ti.com; bbrezillon@kernel.org; yamada.masahiro@socionext.com; linux-
> mtd@lists.infradead.org; linux-kernel@vger.kernel.org
> Subject: Re: [LINUX PATCH v17 1/2] mtd: rawnand: nand_micron: Do not over write
> driver's read_page()/write_page()
>
> On Wed, 26 Jun 2019 11:51:12 +0000
> Naga Sureshkumar Relli <nagasure@xilinx.com> wrote:
>
> > Hi Boris,
> >
> > > -----Original Message-----
> > > From: Boris Brezillon <boris.brezillon@collabora.com>
> > > Sent: Wednesday, June 26, 2019 4:57 PM
> > > To: Naga Sureshkumar Relli <nagasure@xilinx.com>
> > > Cc: miquel.raynal@bootlin.com; helmut.grohne@intenta.de;
> > > richard@nod.at; dwmw2@infradead.org; computersforpeace@gmail.com;
> > > marek.vasut@gmail.com; vigneshr@ti.com; bbrezillon@kernel.org;
> > > yamada.masahiro@socionext.com; linux- mtd@lists.infradead.org;
> > > linux-kernel@vger.kernel.org
> > > Subject: Re: [LINUX PATCH v17 1/2] mtd: rawnand: nand_micron: Do not
> > > over write driver's read_page()/write_page()
> > >
> > > On Wed, 26 Jun 2019 11:22:33 +0000
> > > Naga Sureshkumar Relli <nagasure@xilinx.com> wrote:
> > >
> > > > Hi Boris,
> > > >
> > > > > -----Original Message-----
> > > > > From: Boris Brezillon <boris.brezillon@collabora.com>
> > > > > Sent: Wednesday, June 26, 2019 12:18 PM
> > > > > To: Naga Sureshkumar Relli <nagasure@xilinx.com>
> > > > > Cc: miquel.raynal@bootlin.com; helmut.grohne@intenta.de;
> > > > > richard@nod.at; dwmw2@infradead.org;
> > > > > computersforpeace@gmail.com; marek.vasut@gmail.com;
> > > > > vigneshr@ti.com; bbrezillon@kernel.org;
> > > > > yamada.masahiro@socionext.com; linux- mtd@lists.infradead.org;
> > > > > linux-kernel@vger.kernel.org
> > > > > Subject: Re: [LINUX PATCH v17 1/2] mtd: rawnand: nand_micron: Do
> > > > > not over write driver's read_page()/write_page()
> > > > >
> > > > > On Mon, 24 Jun 2019 22:46:29 -0600 Naga Sureshkumar Relli
> > > > > <naga.sureshkumar.relli@xilinx.com> wrote:
> > > > >
> > > > > > Add check before assigning chip->ecc.read_page() and
> > > > > > chip->ecc.write_page()
> > > > > >
> > > > > > Signed-off-by: Naga Sureshkumar Relli
> > > > > > <naga.sureshkumar.relli@xilinx.com>
> > > > > > ---
> > > > > > drivers/mtd/nand/raw/nand_micron.c | 7 +++++--
> > > > > > 1 file changed, 5 insertions(+), 2 deletions(-)
> > > > > >
> > > > > > diff --git a/drivers/mtd/nand/raw/nand_micron.c
> > > > > > b/drivers/mtd/nand/raw/nand_micron.c
> > > > > > index cbd4f09ac178..565f2696c747 100644
> > > > > > --- a/drivers/mtd/nand/raw/nand_micron.c
> > > > > > +++ b/drivers/mtd/nand/raw/nand_micron.c
> > > > > > @@ -500,8 +500,11 @@ static int micron_nand_init(struct nand_chip *chip)
> > > > > > chip->ecc.size = 512;
> > > > > > chip->ecc.strength = chip->base.eccreq.strength;
> > > > > > chip->ecc.algo = NAND_ECC_BCH;
> > > > > > - chip->ecc.read_page = micron_nand_read_page_on_die_ecc;
> > > > > > - chip->ecc.write_page = micron_nand_write_page_on_die_ecc;
> > > > > > + if (!chip->ecc.read_page)
> > > > > > + chip->ecc.read_page = micron_nand_read_page_on_die_ecc;
> > > > > > +
> > > > > > + if (!chip->ecc.write_page)
> > > > > > + chip->ecc.write_page = micron_nand_write_page_on_die_ecc;
> > > > >
> > > > > That's wrong, if you don't want on-die ECC to be used, simply
> > > > > don't set nand-ecc-mode to "on- die".
> > > > Ok. But if we want to use on-die ECC then you mean to say it is
> > > > mandatory to use
> > > micron_nand_read/write_page_on_die_ecc()?
> > >
> > > Absolutely, and if it doesn't work that means you driver does not
> > > implement raw accesses correctly, which means it's still buggy...
> > I agree. But let's say, if there is a limitation with the controller. Then it is must to have this
> check right?
> > I mean, for pl353 controller, we must clear the CS during the data
> > phase, hence we are splitting the Transfer in the pl353_read/write_page_raw().
> > + pl353_nand_read_data_op(chip, buf, mtd->writesize, false);
> > + p = chip->oob_poi;
> > + pl353_nand_read_data_op(chip, p,
> > + (mtd->oobsize -
> > + PL353_NAND_LAST_TRANSFER_LENGTH), false);
> > + p += (mtd->oobsize - PL353_NAND_LAST_TRANSFER_LENGTH);
> > + xnfc->dataphase_addrflags |= PL353_NAND_CLEAR_CS;
> > + pl353_nand_read_data_op(chip, p, PL353_NAND_LAST_TRANSFER_LENGTH,
> > + false);
> > As the above sequence is needed even for raw access, PL353 is unable to use the on_die_page
> reads.
>
> This "de-assert CS on last access" logic should be done in the
> exec_op() implementation. I also wonder how that works for operations that don't have data
> cycles. Oh, BTW, most chips are CE-don't-care, which means you can assert/de-assert CS on
> each read_data_op() without any issues.
Yes, we can assert/de-assert CS on each read/write_data_op().
But what about transfer length splitting?
+ p = chip->oob_poi;
+ pl353_nand_read_data_op(chip, p,
+ (mtd->oobsize -
+ PL353_NAND_LAST_TRANSFER_LENGTH), false);
+ p += (mtd->oobsize - PL353_NAND_LAST_TRANSFER_LENGTH);
This should be done as a part of pl353_raw_read/write() right?
Thanks,
Naga Sureshkumar Relli
next prev parent reply other threads:[~2019-06-26 12:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 4:46 [LINUX PATCH v17 1/2] mtd: rawnand: nand_micron: Do not over write driver's read_page()/write_page() Naga Sureshkumar Relli
2019-06-25 4:46 ` [LINUX PATCH v17 2/2] mtd: rawnand: pl353: Add basic driver for arm pl353 smc nand interface Naga Sureshkumar Relli
2019-06-25 14:11 ` Helmut Grohne
2019-07-03 6:13 ` Naga Sureshkumar Relli
2019-07-03 6:25 ` Boris Brezillon
2019-07-03 8:57 ` Naga Sureshkumar Relli
2019-07-03 11:06 ` Boris Brezillon
2019-07-03 11:29 ` Naga Sureshkumar Relli
2019-07-03 11:40 ` Boris Brezillon
2019-06-25 14:11 ` [LINUX PATCH v17 1/2] mtd: rawnand: nand_micron: Do not over write driver's read_page()/write_page() Helmut Grohne
2019-06-26 6:48 ` Boris Brezillon
2019-06-26 11:22 ` Naga Sureshkumar Relli
2019-06-26 11:27 ` Boris Brezillon
2019-06-26 11:51 ` Naga Sureshkumar Relli
2019-06-26 12:04 ` Boris Brezillon
2019-06-26 12:12 ` Naga Sureshkumar Relli [this message]
2019-06-26 12:20 ` Boris Brezillon
2019-06-26 12:33 ` Naga Sureshkumar Relli
2019-07-08 12:18 ` Naga Sureshkumar Relli
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=DM6PR02MB4779B5C815FB4DAF33EF4996AFE20@DM6PR02MB4779.namprd02.prod.outlook.com \
--to=nagasure@xilinx.com \
--cc=bbrezillon@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=helmut.grohne@intenta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=yamada.masahiro@socionext.com \
/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;
as well as URLs for NNTP newsgroup(s).