public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Huang Shijie <b32955@freescale.com>
To: <dwmw2@infradead.org>
Cc: Huang Shijie <b32955@freescale.com>,
	computersforpeace@gmail.com, linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org, dedekind1@gmail.com
Subject: [PATCH V3 6/9] mtd: add a new field for ecc info in the nand_flash_dev{}
Date: Tue, 23 Apr 2013 16:54:54 +0800	[thread overview]
Message-ID: <1366707297-31309-7-git-send-email-b32955@freescale.com> (raw)
In-Reply-To: <1366707297-31309-1-git-send-email-b32955@freescale.com>

Add the @ecc_info in the nand_flash_dev{}.
The lower 16 bits are used to store the ECC bits, while the upper 16 bits
are used to store the ECC data chunk size.

Signed-off-by: Huang Shijie <b32955@freescale.com>
---
 include/linux/mtd/nand.h |   10 ++++++++++
 1 files changed, 10 insertions(+), 0 deletions(-)

diff --git a/include/linux/mtd/nand.h b/include/linux/mtd/nand.h
index 063e517..f4c7777 100644
--- a/include/linux/mtd/nand.h
+++ b/include/linux/mtd/nand.h
@@ -624,6 +624,10 @@ struct nand_chip {
 	{ .name = (nm), {{ .dev_id = (devid) }}, .chipsize = (chipsz), \
 	  .options = (opts) }
 
+#define NAND_ECC_INFO(strength, size)	(((strength) << 16) | (size))
+#define NAND_ECC_STRENGTH(x)		(((x) >> 16) & 0xffff)
+#define NAND_ECC_SIZE(x)		((x) & 0xffff)
+
 /**
  * struct nand_flash_dev - NAND Flash Device ID Structure
  * @name: a human-readable name of the NAND chip
@@ -641,6 +645,11 @@ struct nand_chip {
  * @options: stores various chip bit options
  * @id_len: The valid length of the @id.
  * @oobsize: OOB size
+ * @ecc_info: The ECC information.
+ *            lower 16 bits: store the ECC bits.
+ *            upper 16 bits: store the ECC data chunk size.
+ *            For example, the "4bit ECC for each 512Byte" can be set with
+ *            NAND_ECC_INFO(4, 512) macro.
  */
 struct nand_flash_dev {
 	char *name;
@@ -657,6 +666,7 @@ struct nand_flash_dev {
 	unsigned int options;
 	uint16_t id_len;
 	uint16_t oobsize;
+	uint32_t ecc_info;
 };
 
 /**
-- 
1.7.1

  parent reply	other threads:[~2013-04-23  9:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23  8:54 [PATCH V3 0/9] mtd: add datasheet's ECC information to nand_chip{} Huang Shijie
2013-04-23  8:54 ` [PATCH V3 1/9] mtd: add more comment for ecc_strength/ecc_size Huang Shijie
2013-04-25  6:32   ` Brian Norris
2013-04-25  6:39     ` Huang Shijie
2013-04-25  6:40     ` Huang Shijie
2013-04-23  8:54 ` [PATCH V3 2/9] mtd: add data structures for Extended Parameter Page Huang Shijie
2013-04-23  8:54 ` [PATCH V3 3/9] mtd: add a helper to get the supported features for ONFI nand Huang Shijie
2013-04-23  8:54 ` [PATCH V3 4/9] mtd: get the ECC info from the Extended Parameter Page Huang Shijie
2013-04-25  6:20   ` Brian Norris
2013-04-25  6:38     ` Huang Shijie
2013-04-23  8:54 ` [PATCH V3 5/9] mtd: replace the hardcode with the onfi_feature() Huang Shijie
2013-04-23  8:54 ` Huang Shijie [this message]
2013-04-25  6:57   ` [PATCH V3 6/9] mtd: add a new field for ecc info in the nand_flash_dev{} Brian Norris
2013-04-25  8:56     ` Huang Shijie
2013-04-26  6:15       ` Brian Norris
2013-04-26  6:24         ` Huang Shijie
2013-04-23  8:54 ` [PATCH V3 7/9] mtd: parse out the ECC info for the full-id nand chips Huang Shijie
2013-04-23  8:54 ` [PATCH V3 8/9] mtd: add the ecc info for some " Huang Shijie
2013-04-23  8:54 ` [PATCH V3 9/9] mtd: gpmi: set the BCH's geometry with the ecc info Huang Shijie
2013-04-25  6:40 ` [PATCH V3 0/9] mtd: add datasheet's ECC information to nand_chip{} Brian Norris
2013-04-25  6:45   ` 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=1366707297-31309-7-git-send-email-b32955@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