public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Huang Shijie <shijie8@gmail.com>
Cc: Huang Shijie <b32955@freescale.com>,
	linux-mtd@lists.infradead.org, dwmw2@infradead.org, pekon@ti.com,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH v4 6/6] mtd: update the ABI document about the ecc step size
Date: Sat, 17 Aug 2013 11:14:47 -0700	[thread overview]
Message-ID: <20130817181447.GC5034@norris.computersforpeace.net> (raw)
In-Reply-To: <20130817032644.GA27332@gmail.com>

On Fri, Aug 16, 2013 at 11:26:47PM -0400, Huang Shijie wrote:
> On Fri, Aug 16, 2013 at 04:45:59PM +0300, Artem Bityutskiy wrote:
> > On Fri, 2013-08-16 at 10:10 +0800, Huang Shijie wrote:
> > > +
> > > +What:          /sys/class/mtd/mtdX/ecc_step_size
> > > +Date:          May 2013
> > > +KernelVersion: 3.10
> > > +Contact:       linux-mtd@lists.infradead.org
> > > +Description:
> > > +               The size of each ECC step which is used for ECC.
> > > +               Note that some devices will have multiple ecc steps within each
> > > +               writesize region.
> > 
> > Actually this phrase is a bit confusing because it may be interpreted as
> > that one write-size may have ECC steps of multiple sizes. Would you
> > re-phrase, may be?
> What's about the following:
>  -----------------------------------------------------------------
>    The size of each ECC step which is used for ECC.
>    Note that some devices will have multiple ecc steps within each
>    writesize region, and the ecc steps share the same size.
>  -----------------------------------------------------------------

I took pieces of your message and rewrote it myself. Diff pasted below
(I edited ecc_strength to be less redundant and added a few details that
were worth mentioning). Let me know if you want to revise it, but I'll
push it to l2-mtd.git.

Brian

---
 Documentation/ABI/testing/sysfs-class-mtd | 18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)

diff --git a/Documentation/ABI/testing/sysfs-class-mtd b/Documentation/ABI/testing/sysfs-class-mtd
index 3105644..a795582 100644
--- a/Documentation/ABI/testing/sysfs-class-mtd
+++ b/Documentation/ABI/testing/sysfs-class-mtd
@@ -128,9 +128,8 @@ KernelVersion:	3.4
 Contact:	linux-mtd@lists.infradead.org
 Description:
 		Maximum number of bit errors that the device is capable of
-		correcting within each region covering an ecc step.  This will
-		always be a non-negative integer.  Note that some devices will
-		have multiple ecc steps within each writesize region.
+		correcting within each region covering an ECC step (see
+		ecc_step_size).  This will always be a non-negative integer.
 
 		In the case of devices lacking any ECC capability, it is 0.
 
@@ -173,3 +172,16 @@ Description:
 		This is generally applicable only to NAND flash devices with ECC
 		capability.  It is ignored on devices lacking ECC capability;
 		i.e., devices for which ecc_strength is zero.
+
+What:		/sys/class/mtd/mtdX/ecc_step_size
+Date:		May 2013
+KernelVersion:	3.10
+Contact:	linux-mtd@lists.infradead.org
+Description:
+		The size of a single region covered by ECC, known as the ECC
+		step.  Devices may have several equally sized ECC steps within
+		each writesize region.  The step size counts only the data area,
+		not the spare area.
+
+		It will always be a non-negative integer.  In the case of
+		devices lacking any ECC capability, it is 0.

  reply	other threads:[~2013-08-17 18:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16  2:10 [PATCH v4 0/6] Export the ECC step size to user applications Huang Shijie
2013-08-16  2:10 ` [PATCH v4 1/6] mtd: add a new field to mtd_info{} Huang Shijie
2013-08-16  2:10 ` [PATCH v4 2/6] mtd: add a new sys node to show the ecc step size Huang Shijie
2013-08-16  2:10 ` [PATCH v4 3/6] mtd: set the ecc step size for master/slave mtd_info Huang Shijie
2013-08-16  2:10 ` [PATCH v4 4/6] mtd: set ONFI nand's default hooks in nand_set_defaults() Huang Shijie
2013-08-17 17:55   ` Brian Norris
2013-08-19  8:06     ` Brian Foster
2013-08-20  0:41       ` Brian Norris
2013-08-20  7:09         ` Brian Foster
2013-08-16  2:10 ` [PATCH v4 5/6] mtd: gpmi: remove the nand_scan() Huang Shijie
2013-08-16  2:10 ` [PATCH v4 6/6] mtd: update the ABI document about the ecc step size Huang Shijie
2013-08-16 13:45   ` Artem Bityutskiy
2013-08-17  3:26     ` Huang Shijie
2013-08-17 18:14       ` Brian Norris [this message]
2013-08-18 14:29         ` Huang Shijie
2013-08-20  1:02           ` Brian Norris
2013-08-20  2:11             ` Huang Shijie
2013-08-17 18:35 ` [PATCH v4 0/6] Export the ECC step size to user applications Brian Norris
2013-08-18 14:48   ` Huang Shijie

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=20130817181447.GC5034@norris.computersforpeace.net \
    --to=computersforpeace@gmail.com \
    --cc=b32955@freescale.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@ti.com \
    --cc=shijie8@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox