From: Alexander Dahl <ada@thorsis.com>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Cc: Eugen Hristev <eugen.hristev@linaro.org>,
Zixun LI <admin@hifiphile.com>,
Balamanikandan Gunasundar
<balamanikandan.gunasundar@microchip.com>,
u-boot@lists.denx.de,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Tom Rini <trini@konsulko.com>, Alexander Dahl <ada@thorsis.com>
Subject: Re: [PATCH 2/2] mtd: rawnand: atmel: Remove timing from atmel_pmecc struct
Date: Fri, 7 Nov 2025 12:17:37 +0100 [thread overview]
Message-ID: <20251107-sandpaper-blaming-e68f3c89ccc0@thorsis.com> (raw)
In-Reply-To: <CAOf5uwkZUnUSjJ=CqtZhVf-rQ31eU4gC5o+XDXKJEAtRrY4NKQ@mail.gmail.com>
Hello Michael,
Am Fri, Nov 07, 2025 at 12:04:16PM +0100 schrieb Michael Nazzareno Trimarchi:
> Hi
>
> On Fri, Nov 7, 2025 at 11:56 AM Eugen Hristev <eugen.hristev@linaro.org> wrote:
> >
> >
> >
> > On 11/6/25 13:12, Zixun LI wrote:
> > > "timing" is unused in atmel_pmecc struct, also it's not exist in Linux
> > > driver, let's remove it.
> > >
> > > Signed-off-by: Zixun LI <admin@hifiphile.com>
> > > ---
> > > drivers/mtd/nand/raw/atmel/pmecc.c | 2 --
> > > drivers/mtd/nand/raw/atmel/pmecc.h | 1 -
> > > 2 files changed, 3 deletions(-)
> > >
> > > diff --git a/drivers/mtd/nand/raw/atmel/pmecc.c b/drivers/mtd/nand/raw/atmel/pmecc.c
> > > index 7c4e9bd5f9967b119239adf2b39e683ea62b71fd..8fc5614cc0091d3e0f4b9280beee9e684fe2a57d 100644
> > > --- a/drivers/mtd/nand/raw/atmel/pmecc.c
> > > +++ b/drivers/mtd/nand/raw/atmel/pmecc.c
> > > @@ -839,8 +839,6 @@ atmel_pmecc_create(struct udevice *dev,
> > > ofnode_read_resource(dev->node_, 1, &res);
> > > pmecc->regs.errloc = (void *)res.start;
> > >
> > > - pmecc->regs.timing = 0;
> > > -
> >
> > I see there is also an unused parameter to atmel_pmecc_create() called
> > timing_res_idx .
> > Maybe this parameter was intended to be passed to the timing mapped memory ?
> >
> > If the timing_res_idx is related and unused as well, isn't it supposed
> > to be removed together ?
> >
> > I see it's being called with a hardcoded "2" , does this have any
> > significance that you know of ? Or it can be safely removed.
> >
> > Eugen
> >
> > > /* pmecc data setup time */
> > > if (caps->clk_ctrl)
> > > writel(PMECC_CLK_133MHZ, pmecc->regs.base + ATMEL_PMECC_CLK);
> > > diff --git a/drivers/mtd/nand/raw/atmel/pmecc.h b/drivers/mtd/nand/raw/atmel/pmecc.h
> > > index 43f96b2f168c7b88e0c907996f2ae64f8554ed58..88b0d18040e7c48f226c74ce9b5caf93b5760360 100644
> > > --- a/drivers/mtd/nand/raw/atmel/pmecc.h
> > > +++ b/drivers/mtd/nand/raw/atmel/pmecc.h
> > > @@ -65,7 +65,6 @@ struct atmel_pmecc {
> > > struct {
> > > void __iomem *base;
> > > void __iomem *errloc;
> > > - void __iomem *timing;
> > > } regs;
> > >
> > > /* Mutex used for pmecc enable/disable */
> > >
> >
> I'm willing to help to clock part of nand, can someone point where I
> can buy the board?
I use the Microchip SAM9X60 Curiosity:
https://www.microchip.com/en-us/development-tool/ev40e67a
It's also available from Mouser, RS, Digikey, and probably more.
The NAND flash populated on that board is an MX30LF4G28AD-XKI [1].
Greets
Alex
[1] https://www.mxic.com.tw/en-us/products/NAND-Flash/SLC-NAND-Flash/Pages/spec.aspx?p=MX30LF4G28AD&m=SLC+NAND&n=PM2579
next prev parent reply other threads:[~2025-11-07 11:17 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
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 [this message]
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=20251107-sandpaper-blaming-e68f3c89ccc0@thorsis.com \
--to=ada@thorsis.com \
--cc=admin@hifiphile.com \
--cc=balamanikandan.gunasundar@microchip.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=eugen.hristev@linaro.org \
--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