From: Huang Shijie <b32955@freescale.com>
To: <dwmw2@infradead.org>
Cc: <dedekind1@gmail.com>, <computersforpeace@gmail.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
Huang Shijie <b32955@freescale.com>
Subject: [PATCH V3 2/3] mtd: add a new table for the unparsable nand chips
Date: Mon, 28 Jan 2013 12:57:18 +0800 [thread overview]
Message-ID: <1359349039-11510-3-git-send-email-b32955@freescale.com> (raw)
In-Reply-To: <1359349039-11510-1-git-send-email-b32955@freescale.com>
We have 4 Toshiba nand chips which can not be parsed out by the
id data. Add a new table for the unparsable nand chips.
It makes mess if we add these entries to the nand_flash_ids table.
The entries in the nand_flash_ids stands for a class of nand chips.
But the unparsable nand chips are just some singular chips.
Signed-off-by: Huang Shijie <b32955@freescale.com>
---
drivers/mtd/nand/nand_ids.c | 21 +++++++++++++++++++++
include/linux/mtd/nand.h | 1 +
2 files changed, 22 insertions(+), 0 deletions(-)
diff --git a/drivers/mtd/nand/nand_ids.c b/drivers/mtd/nand/nand_ids.c
index 99949f6..4147c78 100644
--- a/drivers/mtd/nand/nand_ids.c
+++ b/drivers/mtd/nand/nand_ids.c
@@ -12,6 +12,27 @@
#include <linux/mtd/nand.h>
#include <linux/sizes.h>
+/* This table uses the full ID data as the keyword. */
+struct nand_flash_dev nand_flash_full_ids[] = {
+ /* TOSHIBA */
+ {"TC58NVG2S0F 4G 3.3V 8-bit ",
+ {0x98, 0xdc, 0x90, 0x26, 0x76, 0x15, 0x01, 0x08},
+ SZ_4K, SZ_512, SZ_256K, 0, 8, 224},
+ {"TC58NVG3S0F 8G 3.3V 8-bit ",
+ {0x98, 0xd3, 0x90, 0x26, 0x76, 0x15, 0x02, 0x08},
+ SZ_4K, SZ_1K, SZ_256K, 0, 8, 232},
+ {"TC58NVG5D2 32G 3.3V 8-bit ",
+ {0x98, 0xd7, 0x94, 0x32, 0x76, 0x56, 0x09, 0x00},
+ SZ_8K, SZ_4K, SZ_1M, 0, 8, 640},
+ {"TC58NVG6D2 64G 3.3V 8-bit ",
+ {0x98, 0xde, 0x94, 0x82, 0x76, 0x56, 0x04, 0x20},
+ SZ_8K, SZ_8K, SZ_2M, 0, 8, 640},
+
+ /* end here */
+ {NULL,}
+};
+
+
/*
* Chip ID list
*
diff --git a/include/linux/mtd/nand.h b/include/linux/mtd/nand.h
index d8fd638..119c8e0 100644
--- a/include/linux/mtd/nand.h
+++ b/include/linux/mtd/nand.h
@@ -618,6 +618,7 @@ struct nand_manufacturers {
};
extern struct nand_flash_dev nand_flash_ids[];
+extern struct nand_flash_dev nand_flash_full_ids[];
extern struct nand_manufacturers nand_manuf_ids[];
extern int nand_scan_bbt(struct mtd_info *mtd, struct nand_bbt_descr *bd);
--
1.7.0.4
next prev parent reply other threads:[~2013-01-28 5:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 4:57 [PATCH V3 0/3] mtd: use the full-id as the keyword Huang Shijie
2013-01-28 4:57 ` [PATCH V3 1/3] mtd: add new fields to nand_flash_dev{} Huang Shijie
2013-02-12 15:47 ` Artem Bityutskiy
2013-02-16 3:56 ` Huang Shijie
2013-03-02 14:21 ` Artem Bityutskiy
2013-03-04 5:57 ` Huang Shijie
2013-03-04 7:50 ` Artem Bityutskiy
2013-03-04 8:08 ` Huang Shijie
2013-03-04 8:24 ` Artem Bityutskiy
2013-03-04 8:40 ` Huang Shijie
2013-03-04 8:46 ` Artem Bityutskiy
2013-03-04 8:59 ` Huang Shijie
2013-03-04 19:27 ` Brian Norris
2013-08-08 18:38 ` Brian Norris
2013-03-04 8:37 ` Artem Bityutskiy
2013-03-04 8:57 ` Huang Shijie
2013-02-28 8:25 ` Huang Shijie
2013-03-02 14:19 ` Artem Bityutskiy
2013-03-04 3:06 ` Huang Shijie
2013-01-28 4:57 ` Huang Shijie [this message]
2013-01-28 4:57 ` [PATCH V3 3/3] mtd: add the new detection method for the unparsable nand chips 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=1359349039-11510-3-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;
as well as URLs for NNTP newsgroup(s).