From: Huang Shijie <shijie8@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Huang Shijie <b32955@freescale.com>,
dwmw2@infradead.org, artem.bityutskiy@linux.intel.com,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/3] mtd: add 4 Toshiba nand chips for the full-id case
Date: Thu, 14 Mar 2013 22:29:30 -0400 [thread overview]
Message-ID: <5142878A.7050701@gmail.com> (raw)
In-Reply-To: <CAN8TOE9aGckZ2PrCCPQe4ZgW6Aph3otXGohNuRPssu8f302xaA@mail.gmail.com>
于 2013年03月14日 01:10, Brian Norris 写道:
> On Wed, Mar 13, 2013 at 7:59 PM, Huang Shijie<b32955@freescale.com> wrote:
>> I have 4 Toshiba nand chips which can not be parsed out by the
>> id data. We can not get the oob size from the id data. So add them
>> as the full-id nand chips in the first of nand_flash_ids.
>>
>> The nand_get_flash_type() scans the full id nands firstly.
>> If a full-id nand matchs, it will not continue to parse other
>> non-full-id nand types, else it will continue to parse the non-full-id nands.
>>
>> Signed-off-by: Huang Shijie<b32955@freescale.com>
>> ---
>> drivers/mtd/nand/nand_ids.c | 22 ++++++++++++++++++++++
>> 1 files changed, 22 insertions(+), 0 deletions(-)
>>
>> diff --git a/drivers/mtd/nand/nand_ids.c b/drivers/mtd/nand/nand_ids.c
>> index 625bc89..38b8cee 100644
>> --- a/drivers/mtd/nand/nand_ids.c
>> +++ b/drivers/mtd/nand/nand_ids.c
>> @@ -10,6 +10,7 @@
>> */
>> #include<linux/module.h>
>> #include<linux/mtd/nand.h>
>> +#include<linux/sizes.h>
>>
>> #define LP_OPTIONS NAND_SAMSUNG_LP_OPTIONS
>> #define LP_OPTIONS16 (LP_OPTIONS | NAND_BUSWIDTH_16)
>> @@ -22,6 +23,27 @@
>> * extended chip ID.
>> */
>> struct nand_flash_dev nand_flash_ids[] = {
>> + /*
>> + * The full-id nands may share the same Device ID with the non-full-id
>> + * nands. In order to distinguish the two type nands, we put the
>> + * full-id nands in the first of the table. So the nand_get_flash_type()
>> + * scans the full id nands firstly. If a full-id nand matchs, it will
>> + * not continue to parse other non-full-id nand types, else it will
>> + * continue to parse the non-full-id nands.
>> + */
> There are a few grammar/language issues (nands -> NAND chips, id ->
> ID, firstly -> first). Also, I don't think you need to explain the
> full search here. I would rewrite this whole paragraph as:
>
sorry for my poor english.
> "Some incompatible NAND chips share device ID's and so must be listed
> by full ID. We list them first so that we can easily identify the most
> specific match."
>
thanks. I will use this description.
Huang Shijie
next prev parent reply other threads:[~2013-03-14 13:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 2:59 [PATCH v5 0/3] mtd: use the full-id as the keyword for some nand chips Huang Shijie
2013-03-14 2:59 ` [PATCH v5 1/3] mtd: add a new field for nand_flash_dev{} Huang Shijie
2013-03-14 2:59 ` [PATCH v5 2/3] mtd: add the support to parse out the full-id nand type Huang Shijie
2013-03-14 5:17 ` Brian Norris
2013-03-14 2:59 ` [PATCH v5 3/3] mtd: add 4 Toshiba nand chips for the full-id case Huang Shijie
2013-03-14 5:10 ` Brian Norris
2013-03-15 2:29 ` Huang Shijie [this message]
2013-03-15 7:21 ` Brian Norris
2013-03-14 4:48 ` [PATCH v5 0/3] mtd: use the full-id as the keyword for some nand chips Brian Norris
2013-03-14 7:07 ` Artem Bityutskiy
2013-03-14 7:37 ` Brian Norris
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=5142878A.7050701@gmail.com \
--to=shijie8@gmail.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=b32955@freescale.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