From: Eugen Hristev <eugen.hristev@linaro.org>
To: Zixun LI <admin@hifiphile.com>, Alexander Dahl <ada@thorsis.com>
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
u-boot@lists.denx.de,
Michael Trimarchi <michael@amarulasolutions.com>,
Tom Rini <trini@konsulko.com>,
Balamanikandan Gunasundar
<balamanikandan.gunasundar@microchip.com>
Subject: Re: [PATCH 1/2] mtd: rawnand: atmel: set pmecc data setup time
Date: Fri, 7 Nov 2025 12:52:05 +0200 [thread overview]
Message-ID: <e0a9b9af-330c-4504-8ef3-ba4c3433ce4f@linaro.org> (raw)
In-Reply-To: <20251106-pmecc-v1-1-a1f3cf430be9@hifiphile.com>
Hello Zixun, Alexander,
On 11/6/25 13:12, Zixun LI wrote:
> Setup the pmecc data setup time as 3 clock cycles for 133MHz as
> recommended by the datasheet.
>
> Backported from Linux: f552a7c7 ("mtd: rawnand: atmel: set pmecc data
> setup time")
Maybe use 12 digits commit hash ? I cannot find this commit in Linux
>
> Fixes: a490e1b7c017c ("nand: atmel: Add pmecc driver")
>
> Signed-off-by: Zixun LI <admin@hifiphile.com>
> ---
> drivers/mtd/nand/raw/atmel/pmecc.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/drivers/mtd/nand/raw/atmel/pmecc.c b/drivers/mtd/nand/raw/atmel/pmecc.c
> index e500a0fe3f8671ff08195c94c3383696a7731eb3..7c4e9bd5f9967b119239adf2b39e683ea62b71fd 100644
> --- a/drivers/mtd/nand/raw/atmel/pmecc.c
> +++ b/drivers/mtd/nand/raw/atmel/pmecc.c
> @@ -142,6 +142,7 @@ struct atmel_pmecc_caps {
> int nstrengths;
> int el_offset;
> bool correct_erased_chunks;
> + bool clk_ctrl;
> };
>
> struct atmel_pmecc_user_conf_cache {
> @@ -840,6 +841,10 @@ atmel_pmecc_create(struct udevice *dev,
>
> pmecc->regs.timing = 0;
>
> + /* pmecc data setup time */
> + if (caps->clk_ctrl)
> + writel(PMECC_CLK_133MHZ, pmecc->regs.base + ATMEL_PMECC_CLK);
> +
> /* Disable all interrupts before registering the PMECC handler. */
> writel(0xffffffff, pmecc->regs.base + ATMEL_PMECC_IDR);
> atmel_pmecc_reset(pmecc);
> @@ -884,6 +889,7 @@ static struct atmel_pmecc_caps at91sam9g45_caps = {
> .strengths = atmel_pmecc_strengths,
> .nstrengths = 5,
> .el_offset = 0x8c,
> + .clk_ctrl = true,
This appears to be done only for sam9g45.
So, Alexander, this should not impact sam9x60 .
I looked a bit in the Linux driver and this appears to be just as bad:
133 Mhz clock config hardcoded. I would expect this clock to be taken
from a clock input and not hardcoded. But oh well, if this clock is to
be changed in another device, it would be exposed somewhere...
Eugen
> };
>
> static struct atmel_pmecc_caps sama5d4_caps = {
>
next prev parent reply other threads:[~2025-11-07 10:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 11:12 [PATCH 0/2] mtd: rawnand: atmel: Fix ECC error on SAM9 Zixun LI
2025-11-06 11:12 ` [PATCH 1/2] mtd: rawnand: atmel: set pmecc data setup time Zixun LI
2025-11-07 10:52 ` Eugen Hristev [this message]
2025-11-07 11:01 ` Alexander Dahl
2025-11-07 12:53 ` Zixun LI
2025-11-11 10:29 ` Eugen Hristev
2025-11-06 11:12 ` [PATCH 2/2] mtd: rawnand: atmel: Remove timing from atmel_pmecc struct Zixun LI
2025-11-06 16:27 ` Alexander Dahl
2025-11-07 10:56 ` Eugen Hristev
2025-11-07 11:04 ` Michael Nazzareno Trimarchi
2025-11-07 11:17 ` Alexander Dahl
2025-11-07 10:48 ` [PATCH 0/2] mtd: rawnand: atmel: Fix ECC error on SAM9 Eugen Hristev
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=e0a9b9af-330c-4504-8ef3-ba4c3433ce4f@linaro.org \
--to=eugen.hristev@linaro.org \
--cc=ada@thorsis.com \
--cc=admin@hifiphile.com \
--cc=balamanikandan.gunasundar@microchip.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=michael@amarulasolutions.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox