All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
Cc: u-boot@lists.denx.de,
	 Dario Binacchi <dario.binacchi@amarulasolutions.com>,
	 Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH] nand: Add a watch command
Date: Mon, 02 Dec 2024 10:39:07 +0100	[thread overview]
Message-ID: <874j3ma0g4.fsf@bootlin.com> (raw)
In-Reply-To: <CAOf5uwnP4O1cop9_CcBYN0YauvQQ_A0cuhno+PDOQzr2=h=UaQ@mail.gmail.com> (Michael Nazzareno Trimarchi's message of "Tue, 26 Nov 2024 21:19:58 +0100")

Hi Michael,

On 26/11/2024 at 21:19:58 +01, Michael Nazzareno Trimarchi <michael@amarulasolutions.com> wrote:

> Hi Miquel
>
> On Tue, Nov 28, 2023 at 11:56 AM Miquel Raynal
> <miquel.raynal@bootlin.com> wrote:
>>
>> This is a debug command to monitor the retention state of the data on
>> the array. The command needs a duplication of the mtd_read_oob()
>> function to actually return the maximum number of bitflips encountered
>> while reading the page. We could write a specific implementation for the
>> Sunxi driver but this is probably enough.
>>
>>     nand watch <off> <size> - check an area for bitflips
>>     nand watch.part <part> - check a partition for bitflips
>>     nand watch.chip - check the whole device for bitflips
>>
>> The output may be a bit verbose and could look like:
>>
>
> I have rebased and I will take a look on this patch tomorrow. I think having it
> is ok.

Haha, I must admit I forgot about it, but I think it would be nice to
get it in, I used this tool quite a lot for debugging purposes, I am
sure it can be useful to others. :-)

Cheers,
Miquèl

  reply	other threads:[~2024-12-02  9:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 10:56 [PATCH] nand: Add a watch command Miquel Raynal
2024-11-26 20:19 ` Michael Nazzareno Trimarchi
2024-12-02  9:39   ` Miquel Raynal [this message]
2026-04-17  8:24   ` Miquel Raynal
2026-04-17  8:29     ` Michael Nazzareno Trimarchi

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=874j3ma0g4.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=michael@amarulasolutions.com \
    --cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.