public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Huang Shijie <b32955@freescale.com>
To: <dedekind1@gmail.com>
Cc: <dwmw2@infradead.org>, <computersforpeace@gmail.com>,
	<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v5 01/11] mtd: add datasheet's ECC information to nand_chip{}
Date: Thu, 16 May 2013 16:06:16 +0800	[thread overview]
Message-ID: <51949378.6020005@freescale.com> (raw)
In-Reply-To: <1368688465.15764.172.camel@sauron.fi.intel.com>

于 2013年05月16日 15:14, Artem Bityutskiy 写道:
> On Thu, 2013-05-16 at 10:16 +0800, Huang Shijie wrote:
>> 于 2013年05月15日 20:11, Artem Bityutskiy 写道:
>>> On Wed, 2013-05-15 at 16:40 +0800, Huang Shijie wrote:
>>>> + * @ecc_strength:	[INTERN] ECC correctability from the datasheet.
>>>> + *			Minimum amount of bit errors per @ecc_step guaranteed to
>>>> + *			be correctable. If unknown, set to zero.
>>>> + * @ecc_step:		[INTERN] ECC step required by the @ecc_strength,
>>>> + *                      also from the datasheet. It is the recommended ECC step
>>>> + *			size, if known; if unknown, set to zero.
>>> Here and in other places you talk about "datasheet". Do you assume that
>>> the real ECC strength/step used by NAND chips may be different? Or you
>>> assume it must be the same?
>>>
>> The two fields are used to store the ecc info from the datasheet.
>> The two fields are just for a reference.
>>
>> [1] The nand controller may do not use these two fields, it's ok;
>>       For example, the datasheet requires "4bits per 512 bytes".
>>       The nand controller can uses 8bits per 512 bytes.
>>
>>
>> [2] but sometimes the nand controller must use these two fields.
>>       For example, the datasheet requires "40bits per 1024 bytes".
>>       For the hardware limit, the nand controller(BCH) may supports the
>> 40bits ecc in the maximum.
>>       So the nand controller must use these two fields now.
> I wonder if it makes sense to name things so that it is clear form the
> names whether that is the "theoretical" datasheet values or the real
> ones. I would prefer to clearly distinguish between them, in names and
> comments. Thoughts?
>
what's about add the "_datasheet" for these two fields?
such as

ecc_strength__datasheet;ecc_step__datasheet


Huang Shijie



  reply	other threads:[~2013-05-16  8:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15  8:40 [PATCH v5 00/11] mtd: add datasheet's ECC information to nand_chip{} Huang Shijie
2013-05-15  8:40 ` [PATCH v5 01/11] " Huang Shijie
2013-05-15 12:11   ` Artem Bityutskiy
2013-05-16  2:16     ` Huang Shijie
2013-05-16  7:14       ` Artem Bityutskiy
2013-05-16  8:06         ` Huang Shijie [this message]
2013-05-16  9:36           ` Artem Bityutskiy
2013-05-16 10:46             ` Huang Shijie
2013-05-15  8:40 ` [PATCH v5 02/11] mtd: increase max OOB size to 744 Huang Shijie
2013-05-15 12:12   ` Artem Bityutskiy
2013-05-15  8:40 ` [PATCH v5 03/11] mtd: get the ECC info from the parameter page for ONFI nand Huang Shijie
2013-05-15  8:40 ` [PATCH v5 04/11] mtd: add data structures for Extended Parameter Page Huang Shijie
2013-05-15  8:40 ` [PATCH v5 05/11] mtd: add a helper to get the supported features for ONFI nand Huang Shijie
2013-05-15  8:40 ` [PATCH v5 06/11] mtd: get the ECC info from the Extended Parameter Page Huang Shijie
2013-05-15  8:40 ` [PATCH v5 07/11] mtd: replace the hardcode with the onfi_feature() Huang Shijie
2013-05-15  8:40 ` [PATCH v5 08/11] mtd: add ECC info for nand_flash_dev{} Huang Shijie
2013-05-15  8:40 ` [PATCH v5 09/11] mtd: parse out the ECC info for the full-id nand chips Huang Shijie
2013-05-15  8:54 ` [PATCH v5 10/11] mtd: add the ecc info for some " Huang Shijie
2013-05-15  8:54 ` [PATCH v5 11/11] mtd: gpmi: set the BCH's geometry with the ecc info Huang Shijie
2013-05-15 10:05 ` [PATCH v5 00/11] mtd: add datasheet's ECC information to nand_chip{} Artem Bityutskiy

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=51949378.6020005@freescale.com \
    --to=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    /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