From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "Balamanikandan.Gunasundar@microchip.com"
<Balamanikandan.Gunasundar@microchip.com>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"claudiu.beznea@tuxon.dev" <claudiu.beznea@tuxon.dev>,
"nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
"richard@nod.at" <richard@nod.at>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"bbrezillon@kernel.org" <bbrezillon@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] mtd: nand: raw: atmel: Respect tAR, tCLR in read setup timing
Date: Mon, 25 Aug 2025 13:41:05 +0000 [thread overview]
Message-ID: <513ad54017eb96a55176d232ce1464ff51bf452f.camel@siemens.com> (raw)
In-Reply-To: <20250825-vista-cuddle-c159a6bd97ec@thorsis.com>
Hi Alexander,
On Mon, 2025-08-25 at 15:22 +0200, Alexander Dahl wrote:
> > > Threw this on top of 6.12.39-rt11 and tested on two custom platforms
> > > both with a Spansion S34ML02G1 SLC 2GBit flash chip, but with
> > > different SoCs (sama5d2, sam9x60). We had difficulties with the
^^^^^^^^^^^^^^^^^^^
[*]
> > > timing of those NAND flash chips in the past and I wanted to make sure
> > > this patch does not break our setup. Seems fine in a quick test,
> > > reading and writing and reading back is successful.
> >
> > thank you for your feedback!
> >
> > Do you see an opportunity to drop the downstream timing quirks with my patch?
>
> Which downstream do you refer to?
That's how I understood the phrase above, that some adjustments are still required
on your side additionally to standard timings. Sorry for the confusion, if it turns
out to be a misunderstanding on my side!
--
Alexander Sverdlin
Siemens AG
www.siemens.com
next prev parent reply other threads:[~2025-08-25 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 12:00 A. Sverdlin
2025-08-25 11:02 ` Alexander Dahl
2025-08-25 12:21 ` Sverdlin, Alexander
2025-08-25 13:22 ` Alexander Dahl
2025-08-25 13:41 ` Sverdlin, Alexander [this message]
2025-08-26 10:44 ` Alexander Dahl
2025-09-01 12:26 ` 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=513ad54017eb96a55176d232ce1464ff51bf452f.camel@siemens.com \
--to=alexander.sverdlin@siemens.com \
--cc=Balamanikandan.Gunasundar@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=nicolas.ferre@microchip.com \
--cc=richard@nod.at \
--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
all inboxes | Powered by JetHome®