public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mario Kicherer <dev@kicherer.org>
Cc: linux-mtd@lists.infradead.org, richard@nod.at, vigneshr@ti.com,
	Dhruva Gole <d-gole@ti.com>
Subject: Re: [PATCH v2] mtd: spinand: Add support for AllianceMemory AS5F34G04SND
Date: Thu, 26 Jan 2023 15:50:36 +0100	[thread overview]
Message-ID: <20230126155036.532ca8fe@xps-13> (raw)
In-Reply-To: <07c86c5f57145fdc5f06c6f57b8fea84@kicherer.org>

Hello,

dev@kicherer.org wrote on Thu, 26 Jan 2023 15:34:47 +0100:

> Hello Miquèl,
> 
> I made all requested changes and added additional code to make the ooblayout
> functions compatible with all flashes of this series.
> 
> I also ran nandbiterrs with the following result:
> 
> # nandbiterrs -i /dev/mtd11
> incremental biterrors test
> Successfully corrected 0 bit errors per subpage
> Inserted biterror @ 0/5
> Read reported 7 corrected bit errors
> Successfully corrected 1 bit errors per subpage

Yeah, well, I guess we don't have a choice. UBI would see this as a
need to rewrite the block somewhere else because of the too high amount
of bit flips. UBI's threshold is somewhere around 3/4 or the strength,
so these flashes could rapidly wear out, but I don't think we have
another choice.

> Inserted biterror @ 0/2
> Read reported 7 corrected bit errors
> Successfully corrected 2 bit errors per subpage
> Inserted biterror @ 0/0
> Read reported 7 corrected bit errors
> Successfully corrected 3 bit errors per subpage
> Inserted biterror @ 1/7
> Read reported 7 corrected bit errors
> Successfully corrected 4 bit errors per subpage
> Inserted biterror @ 1/5
> Read reported 7 corrected bit errors
> Successfully corrected 5 bit errors per subpage
> Inserted biterror @ 1/2
> Read reported 7 corrected bit errors
> Successfully corrected 6 bit errors per subpage
> Inserted biterror @ 1/0
> Read reported 7 corrected bit errors
> Successfully corrected 7 bit errors per subpage
> Inserted biterror @ 2/6
> Read reported 8 corrected bit errors
> Successfully corrected 8 bit errors per subpage
> Inserted biterror @ 2/5
> Failed to recover 1 bitflips
> Read error after 9 bit errors per page
> 
> I would say this looks good?
> 
> I will send the new patch in a few seconds.
> 
> Thank you!
> Mario
> 


Thanks,
Miquèl

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

      reply	other threads:[~2023-01-26 14:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 16:54 [PATCH v2] mtd: spinand: Add support for AllianceMemory AS5F34G04SND Mario Kicherer
2023-01-23 10:33 ` Miquel Raynal
2023-01-25 12:13   ` Mario Kicherer
2023-01-25 14:27     ` Miquel Raynal
2023-01-25 15:03       ` Mario Kicherer
2023-01-26  8:51         ` Miquel Raynal
2023-01-26 14:34           ` Mario Kicherer
2023-01-26 14:50             ` 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=20230126155036.532ca8fe@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=d-gole@ti.com \
    --cc=dev@kicherer.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