linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Martin Hundebøll" <martin@geanix.com>
Cc: "Rouven Czerwinski" <r.czerwinski@pengutronix.de>,
	"Måns Rullgård" <mans@mansr.com>,
	"Alexander Shiyan" <eagle.alexander923@gmail.com>,
	"Richard Weinberger" <richard@nod.at>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	JaimeLiao <jaimeliao.tw@gmail.com>,
	kernel@pengutronix.de, stable@vger.kernel.org,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	"Sean Nyekjær" <sean@geanix.com>,
	"Domenico Punzo" <dpunzo@micron.com>,
	"Bean Huo" <beanhuo@micron.com>
Subject: Re: [PATCH v2] mtd: rawnand: Ensure the nand chip supports cached reads
Date: Mon, 2 Oct 2023 15:49:43 +0200	[thread overview]
Message-ID: <20231002154943.361e31b0@xps-13> (raw)
In-Reply-To: <b8de26e243afa3e5920455a4d8e5a3451a06d074.camel@geanix.com>

Hi Martin,

martin@geanix.com wrote on Thu, 28 Sep 2023 09:19:56 +0200:

> Hi Miquel,
> 
> On Wed, 2023-09-27 at 17:05 +0200, Miquel Raynal wrote:
> > Hi Martin,
> > 
> > miquel.raynal@bootlin.com wrote on Tue, 26 Sep 2023 13:27:25 +0200:
> >   
> > > Hi Martin,
> > > 
> > > + Bean and Domenico, there is a question for you below.
> > > 
> > > martin@geanix.com wrote on Mon, 25 Sep 2023 13:01:06 +0200:
> > >   
> > > > Hi Rouven,
> > > > 
> > > > On Fri, 2023-09-22 at 16:17 +0200, Rouven Czerwinski wrote:    
> > > > > Both the JEDEC and ONFI specification say that read cache
> > > > > sequential
> > > > > support is an optional command. This means that we not only
> > > > > need to
> > > > > check whether the individual controller supports the command,
> > > > > we also
> > > > > need to check the parameter pages for both ONFI and JEDEC NAND
> > > > > flashes
> > > > > before enabling sequential cache reads.
> > > > > 
> > > > > This fixes support for NAND flashes which don't support
> > > > > enabling
> > > > > cache
> > > > > reads, i.e. Samsung K9F4G08U0F or Toshiba TC58NVG0S3HTA00.
> > > > > 
> > > > > Sequential cache reads are now only available for ONFI and
> > > > > JEDEC
> > > > > devices, if individual vendors implement this, it needs to be
> > > > > enabled
> > > > > per vendor.
> > > > > 
> > > > > Tested on i.MX6Q with a Samsung NAND flash chip that doesn't
> > > > > support
> > > > > sequential reads.
> > > > > 
> > > > > Fixes: 003fe4b9545b ("mtd: rawnand: Support for sequential
> > > > > cache
> > > > > reads")
> > > > > Cc: stable@vger.kernel.org
> > > > > Signed-off-by: Rouven Czerwinski
> > > > > <r.czerwinski@pengutronix.de>      
> > > > 
> > > > Thanks for this. It works as expected for my Toshiba chip,
> > > > obviously
> > > > because it doesn't use ONFI or JEDEC.
> > > > 
> > > > Unfortunately, my Micron chip does use ONFI, and it sets the
> > > > cached-
> > > > read-supported bit. It then fails when reading afterwords:  
> > 
> > I might have over reacted regarding my findings in Micron's
> > datasheet,
> > I need to know if you use the on-die ECC engine or if you use the one
> > on the controller. In the former case the failure is expected. In the
> > latter case, it's not.  
> 
> I use the default, which seems to be the controller engine?

Yeah, you're using the gpmi NAND controller right? If that's the case,
it seems that only ECC correction is supported.

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2023-10-02 13:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22 14:17 [PATCH v2] mtd: rawnand: Ensure the nand chip supports cached reads Rouven Czerwinski
2023-09-25 11:01 ` Martin Hundebøll
2023-09-25 15:19   ` Miquel Raynal
2023-09-26 11:27   ` Miquel Raynal
2023-09-27  6:28     ` [EXT] " Domenico Punzo
2023-09-27  7:20       ` Miquel Raynal
2023-09-27 15:05     ` Miquel Raynal
2023-09-28  7:19       ` Martin Hundebøll
2023-10-02 13:49         ` Miquel Raynal [this message]
2023-10-03 11:29         ` [EXT] " Domenico Punzo
2023-10-03 11:56           ` Miquel Raynal
2023-10-16  9:27 ` Miquel Raynal

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=20231002154943.361e31b0@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=beanhuo@micron.com \
    --cc=dpunzo@micron.com \
    --cc=eagle.alexander923@gmail.com \
    --cc=jaimeliao.tw@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=mans@mansr.com \
    --cc=martin@geanix.com \
    --cc=r.czerwinski@pengutronix.de \
    --cc=richard@nod.at \
    --cc=sean@geanix.com \
    --cc=stable@vger.kernel.org \
    --cc=vigneshr@ti.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).