All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Wu <josh.wu@atmel.com>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: PMECC capability
Date: Fri, 26 Apr 2013 19:01:58 +0800	[thread overview]
Message-ID: <517A5EA6.3010207@atmel.com> (raw)
In-Reply-To: <CACQ1gAhY5TbH3JUYMtRk9ETOLn-ZFNbwKQ_5=j_hnPpZ-1fj_w@mail.gmail.com>

Hi, Richard

On 4/26/2013 6:17 PM, Richard Genoud wrote:
> Hi,
>
> I've got a (dumb?) question about the error correct capability of atmel PMECC:
> Do we have to use the exact error capability required by the nand
> chipset or we can use a bigger one ?

I think it is a very good question and I don't have answer yet.
And it bring up another question: Can the nand flash will got much error 
bits than the ONFI minimum require?
Or the filesystem will make sure this situation rarely happen?

>
> use case:
> I'm working on at91sam9g35-cm board which require 1 bit per 512bytes
> correction and also on a at91sam9g35-cm+phy which require 4bits per
> 512bytes correction.
>
> If I use for both a 4b/512B correction, this won't hurt ?
> There won't be any strange side effect ?

I think it will not hurt. And since PMECC is hardware calculation, 
performance should have no big impaction (I am not test that)

>
> Moreover, as I don't use the OOB data, I could set a 8b/512B correction.
> Will it be completely useless ?

I've seen one of mtd/nand driver (I don't remember the exact name), the 
ECC capability is set as the max one base on the OOB valid size (exclude 
the some used by filesystem).

Just in the moment, I think use the max error correct capability base on 
valid OOB is safer for long time using.

Best Regards,
Josh Wu

>
>
> Regards,
>
> Richard.
>

  reply	other threads:[~2013-04-26 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-26 10:17 PMECC capability Richard Genoud
2013-04-26 11:01 ` Josh Wu [this message]
2013-04-26 11:18   ` Richard Genoud

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=517A5EA6.3010207@atmel.com \
    --to=josh.wu@atmel.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard.genoud@gmail.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 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.