From: Huang Shijie <b32955@freescale.com>
To: <dwmw2@infradead.org>
Cc: artem.bityutskiy@linux.intel.com, computersforpeace@gmail.com,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Huang Shijie <b32955@freescale.com>
Subject: [PATCH V4 1/3] mtd: add new fields to nand_flash_dev{}
Date: Thu, 7 Mar 2013 18:49:22 +0800 [thread overview]
Message-ID: <1362653364-29993-2-git-send-email-b32955@freescale.com> (raw)
In-Reply-To: <1362653364-29993-1-git-send-email-b32955@freescale.com>
As time goes on, we begin to meet the situation that we can not get enough
information from some nand chips's id data. Take some Toshiba's nand chips
for example. I have 4 Toshiba's nand chips in my hand:
TC58NVG2S0F, TC58NVG3S0F, TC58NVG5D2, TC58NVG6D2
When we read these chips' datasheets, we will get the geometry of these chips:
TC58NVG2S0F : 4096 + 224
TC58NVG3S0F : 4096 + 232
TC58NVG5D2 : 8192 + 640
TC58NVG6D2 : 8192 + 640
But we can not parse out the correct oob size for these chips from the id data.
This patch adds some new fields to the nand_flash_dev{}:
@id_len: the valid length of the id data. See the comments in
nand_id_has_period()
@oobsize: the oob size.
Signed-off-by: Huang Shijie <b32955@freescale.com>
---
include/linux/mtd/nand.h | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/include/linux/mtd/nand.h b/include/linux/mtd/nand.h
index 591eeeb..f0a9d93 100644
--- a/include/linux/mtd/nand.h
+++ b/include/linux/mtd/nand.h
@@ -578,6 +578,8 @@ struct nand_chip {
* @erasesize: eraseblock size in bytes (determined from the extended ID if 0)
* @chipsize: total chip size in MiB
* @options: stores various chip bit options
+ * @id_len: The valid length of the @id.
+ * @oobsize: OOB size
*/
struct nand_flash_dev {
char *name;
@@ -592,6 +594,8 @@ struct nand_flash_dev {
unsigned long chipsize;
unsigned long erasesize;
unsigned long options;
+ unsigned long id_len;
+ unsigned long oobsize;
};
/**
--
1.7.1
next prev parent reply other threads:[~2013-03-07 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 10:49 [PATCH V4 0/3] mtd: use the full-id as the keyword for some nand chips Huang Shijie
2013-03-07 10:49 ` Huang Shijie [this message]
2013-03-13 10:54 ` [PATCH V4 1/3] mtd: add new fields to nand_flash_dev{} Artem Bityutskiy
2013-03-13 13:04 ` Huang Shijie
2013-03-13 13:13 ` Artem Bityutskiy
2013-03-14 5:30 ` Brian Norris
2013-03-07 10:49 ` [PATCH V4 2/3] mtd: add 4 Toshiba nand chips for the full-id case Huang Shijie
2013-03-13 10:55 ` Artem Bityutskiy
2013-03-07 10:49 ` [PATCH V4 3/3] mtd: add the support to parse out the full-id nand type 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=1362653364-29993-2-git-send-email-b32955@freescale.com \
--to=b32955@freescale.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=computersforpeace@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