From: Huang Shijie <b32955@freescale.com>
To: Huang Shijie <b32955@freescale.com>
Cc: <dwmw2@infradead.org>, <artem.bityutskiy@linux.intel.com>,
<computersforpeace@gmail.com>, <shmulik.ladkani@gmail.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/3] mtd: add a new table for the unparsable nand chips
Date: Mon, 28 Jan 2013 10:04:30 +0800 [thread overview]
Message-ID: <5105DCAE.8090907@freescale.com> (raw)
In-Reply-To: <1359007901-26464-3-git-send-email-b32955@freescale.com>
于 2013年01月24日 14:11, Huang Shijie 写道:
> 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 | 22 ++++++++++++++++++++++
> include/linux/mtd/nand.h | 1 +
> 2 files changed, 23 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/mtd/nand/nand_ids.c b/drivers/mtd/nand/nand_ids.c
> index 9dc2e54..c1e32d2 100644
> --- a/drivers/mtd/nand/nand_ids.c
> +++ b/drivers/mtd/nand/nand_ids.c
> @@ -11,6 +11,28 @@
> #include <linux/module.h>
> #include <linux/mtd/nand.h>
> #include <linux/sizes.h>
> +#include <linux/sizes.h>
sorry, i added the same header twice.
> +
> +/* 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 5293447..346a389 100644
> --- a/include/linux/mtd/nand.h
> +++ b/include/linux/mtd/nand.h
> @@ -620,6 +620,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);
next prev parent reply other threads:[~2013-01-28 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 6:11 [PATCH v2 0/3] mtd: use the full-id as the keyword Huang Shijie
2013-01-24 6:11 ` [PATCH v2 1/3] mtd: add new fields to nand_flash_dev{} Huang Shijie
2013-01-28 2:06 ` Huang Shijie
2013-02-04 8:42 ` Artem Bityutskiy
2013-02-04 8:46 ` Huang Shijie
2013-01-24 6:11 ` [PATCH v2 2/3] mtd: add a new table for the unparsable nand chips Huang Shijie
2013-01-28 2:04 ` Huang Shijie [this message]
2013-01-24 6:11 ` [PATCH v2 3/3] mtd: add the new detection method " 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=5105DCAE.8090907@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 \
--cc=shmulik.ladkani@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