[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175672957665.48300.9426658311064681547.b4-ty@bootlin.com>
Date: Mon, 01 Sep 2025 14:26:16 +0200
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Boris Brezillon <bbrezillon@...nel.org>, linux-mtd@...ts.infradead.org,
Alexander Sverdlin <alexander.sverdlin@...il.com>
Cc: Balamanikandan.Gunasundar@...rochip.com,
Richard Weinberger <richard@....at>, Vignesh Raghavendra <vigneshr@...com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Claudiu Beznea <claudiu.beznea@...on.dev>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH v2] mtd: nand: raw: atmel: Respect tAR, tCLR in read
setup timing
On Thu, 21 Aug 2025 14:00:57 +0200, A. Sverdlin wrote:
> Having setup time 0 violates tAR, tCLR of some chips, for instance
> TOSHIBA TC58NVG2S3ETAI0 cannot be detected successfully (first ID byte
> being read duplicated, i.e. 98 98 dc 90 15 76 14 03 instead of
> 98 dc 90 15 76 ...).
>
> Atmel Application Notes postulated 1 cycle NRD_SETUP without explanation
> [1], but it looks more appropriate to just calculate setup time properly.
>
> [...]
Applied to mtd/fixes, thanks!
[1/1] mtd: nand: raw: atmel: Respect tAR, tCLR in read setup timing
commit: fd779eac2d659668be4d3dbdac0710afd5d6db12
Patche(s) should be available on mtd/linux.git and will be
part of the next PR (provided that no robot complains by then).
Kind regards,
Miquèl
Powered by blists - more mailing lists