linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Christopher Cordahi <christophercordahi@nanometrics.ca>
Cc: linux-mtd@lists.infradead.org, Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: Question about Davinci NAND using 4 bit ECC
Date: Thu, 20 Jul 2023 08:08:28 +0200	[thread overview]
Message-ID: <20230720080828.1124586b@xps-13> (raw)
In-Reply-To: <CAF_O4Jt3MfYBwd0qF8vv1eHzApEZQOcGhthLCV4suetxYqVacA@mail.gmail.com>

Hi Christopher,

christophercordahi@nanometrics.ca wrote on Wed, 19 Jul 2023 12:34:36
-0400:

> On Tue, 18 Jul 2023 at 04:02, Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> 
> Thanks Miquel for the quick response
> 
> And apologies for sending you the question 3 times.  My first attempt included
> an HTML copy which was rejected by the mailing list, and it took me an extra
> attempt to force my email client to use plain text.  And the third email is
> still awaiting approval by the mailing list moderator, I suspect due to how I
> forwarded and reformatted the original email back to the mailing list.

No problem :)

> > It is hard to tell whether these changes are legitimate or not without
> > properly testing. If you benchmark your changes and never see any
> > error, it does not mean you fall into the pits during your tests.  
> 
> OK, I was hoping to avoid my own testing because as you write, no errors
> doesn't mean it's better.  And I was overly optimistic in hoping for an
> explanation as to why this driver mostly written by TI 15 years ago doesn't
> match their documented procedure.

Probably :-)

> > Observing bitflips in userspace and detecting them can be achieved
> > easily with the nandbiterrs -i tool from the mtd-utils test suite.  
> 
> Thanks for this tip, I'll look into extending the Yocto mtd-utils recipe [1]
> to install it.  I see the kernel also has a nandbiterrs mtd test driver[2].
> Can it be used? Is there any documentation on how to use this kernel test?

The kernel tests are deprecated. You can play with them, just insmod
them in your kernel. They have been reimplemented in userspace to check
the whole mtd stack, and that's the mtd-utils test suite. Prefer using
these.

Yes, adding the debug tools in Yocto might be a good idea. I already
did it for the package in Buildroot.

> [1] https://git.yoctoproject.org/poky/plain/meta/recipes-devtools/mtd/mtd-utils_git.bb
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/mtd/tests/nandbiterrs.c

Thanks,
Miquèl

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

      reply	other threads:[~2023-07-20  6:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAF_O4Js97E_MEK=jrFxUqd4yFOUk4wJg89-LhtDruA67=9_r1A@mail.gmail.com>
     [not found] ` <CAF_O4JuesBTVT806SfMirk2tFG28T7kt5HWSjx9LPEbC9K5zBg@mail.gmail.com>
     [not found]   ` <CAF_O4JvYE8HPQDEmhesndwBsOTk134netTTSYNE-dc0o0ik59A@mail.gmail.com>
2023-07-18  8:02     ` Question about Davinci NAND using 4 bit ECC Miquel Raynal
2023-07-19 16:34       ` Christopher Cordahi
2023-07-20  6:08         ` Miquel Raynal [this message]

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=20230720080828.1124586b@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=christophercordahi@nanometrics.ca \
    --cc=linux-mtd@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).