public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Cheng Ming Lin <linchengming884@gmail.com>
Cc: vigneshr@ti.com, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org, richard@nod.at,
	alvinzhou@mxic.com.tw, leoyu@mxic.com.tw,
	Cheng Ming Lin <chengminglin@mxic.com.tw>
Subject: Re: [PATCH 1/2] mtd: spi-nand: Add fixups for read retry
Date: Tue, 8 Oct 2024 10:55:23 +0200	[thread overview]
Message-ID: <20241008105523.1647f2ca@xps-13> (raw)
In-Reply-To: <CAAyq3SaZKMqJrv7caVwO0+u+nk8JWZ8qTRHdUqQOfQhx9gBF7Q@mail.gmail.com>

Hi,

linchengming884@gmail.com wrote on Tue, 8 Oct 2024 14:25:25 +0800:

> Hi Miquel,
> 
> Miquel Raynal <miquel.raynal@bootlin.com> 於 2024年10月7日 週一 下午4:33寫道:
> >
> > Hi Cheng Ming,
> >  
> > > > > @@ -325,7 +373,8 @@ static const struct spinand_info macronix_spinand_table[] = {
> > > > >                                             &update_cache_variants),
> > > > >                    SPINAND_HAS_QE_BIT,
> > > > >                    SPINAND_ECCINFO(&mx35lfxge4ab_ooblayout,
> > > > > -                                  mx35lf1ge4ab_ecc_get_status)),
> > > > > +                                  mx35lf1ge4ab_ecc_get_status),
> > > > > +                  SPINAND_FIXUPS(&read_retry_fixups)),
> > > > >       SPINAND_INFO("MX35UF1GE4AC",
> > > > >                    SPINAND_ID(SPINAND_READID_METHOD_OPCODE_DUMMY, 0x92, 0x01),
> > > > >                    NAND_MEMORG(1, 2048, 64, 64, 1024, 20, 1, 1, 1),  
> > > >
> > > > I expect a patch targeting the core first, and then the changes in the
> > > > Macronix driver.  
> > >
> > > Got it, so do you prefer that we switch to using flags instead?  
> >
> > Not necessarily, did I?
> >
> > ...
> >  
> 
> Using a flag instead of fixups allows this patch to target the core first,
> and reduces changes in the Macronix driver.

Propose what ever you think is best. You can also look at how it is
done in raw NAND. But always include the core changes first, please.
It is not related to how you implement it.

> 
> > > > >       const struct spinand_manufacturer *manufacturer;
> > > > >       void *priv;
> > > > > +     int read_retries;  
> > > >
> > > > Any reason to keep this variable signed?  
> > >
> > > No, we can simply change from int to u8.  
> >
> > Just unsigned int is fine.
> >  
> 
> Sure, thanks!
> 
> > Thanks,
> > Miquèl  
> 
> Thanks,
> Cheng Ming Lin


Thanks,
Miquèl

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

  reply	other threads:[~2024-10-08  8:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05  5:53 [PATCH 0/2] mtd: spi-nand: Add support for read retry Cheng Ming Lin
2024-09-05  5:53 ` [PATCH 1/2] mtd: spi-nand: Add fixups " Cheng Ming Lin
2024-10-01  9:40   ` Miquel Raynal
2024-10-07  5:49     ` Cheng Ming Lin
2024-10-07  8:33       ` Miquel Raynal
2024-10-08  6:25         ` Cheng Ming Lin
2024-10-08  8:55           ` Miquel Raynal [this message]
2024-10-08  9:19             ` Cheng Ming Lin
2024-09-05  5:53 ` [PATCH 2/2] mtd: spi-nand: Add read retry support Cheng Ming Lin
2024-10-01 10:17   ` Miquel Raynal
2024-10-07  5:53     ` Cheng Ming Lin

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=20241008105523.1647f2ca@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=alvinzhou@mxic.com.tw \
    --cc=chengminglin@mxic.com.tw \
    --cc=leoyu@mxic.com.tw \
    --cc=linchengming884@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --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