All of lore.kernel.org
 help / color / mirror / Atom feed
From: Angus CLARK <angus.clark@st.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH (mtd-www) 05/13] nand-data: remove incorrect/duplicate Numonyx NAND01G devices
Date: Tue, 13 Dec 2011 14:24:47 +0000	[thread overview]
Message-ID: <4EE7602F.30508@st.com> (raw)
In-Reply-To: <CAN8TOE-Mxy1G0LjuqRfO-w1tdESuaDrJ5w=3o68r9C=YfgZ=gg@mail.gmail.com>

Hi Brian,

On 12/09/2011 09:14 PM, Brian Norris wrote:
> On Fri, Dec 9, 2011 at 3:04 AM, Angus CLARK <angus.clark@st.com> wrote:
>> On 12/07/2011 07:28 PM, Brian Norris wrote:
>>> On Tue, Dec 6, 2011 at 4:07 AM, Angus CLARK <angus.clark@st.com> wrote:
>>>> The table includes two entries for each of the following Numonyx devices:
>>>> NAND01GR3B2B, NAND01GW3B2B, NAND01GR4B2B, NAND01GW4B2B.  This patch removes the
>>>> second set since it disagrees with the datasheets I have with regards to ONFI
>>>> V1.0 support and the READID data.
>>>
>>> This one's strange. I have 2 different data sheets for this part (both
>>> Numonyx) and I have a sample NAND that's labeled "ST Micro
>>> NAND01GW3B2C." The sample has ID 0x20F1001D, matching the row for
>>> NAND01GW3B2B which you are deleting. The chip *is* ONFI-capable, and
>>> yields a manufacturer/part string of "ST Micro NAND01GW3B2CN6."
>>>
>>
>> Yes, the "Rev C" version, NAND01GW3B2C, does support ONFI, and returns a READID
>> of 0x20F1001D. (Although interestingly, on my sample, it returns the "ONFI"
>> signature but not the parameter page - I will investigate further!).
> 
> My chip (branded ST) is rev. C and it returns the signature and
> parameter page properly.
> 
>> I do not have an equivalent "Rev B" sample (ie NAND01GW3B2B), but all the
>> information I have suggests the "Rev B" family of devices does not support ONFI,
>> and the READID matches the "first" set of entries in the datasheet.
>>
>> Perhaps this is a "Rev C" vs "Rev B" issue, in which case, I would suggest
>> applying the patch and maybe adding the "Rev C" versions to the table.  What do
>> you think?
> 
> I don't think that's quite right. I'll explain:
> 
> (1) I have two datasheets for this part, with *different* revision
> histories (they don't even have the same origin date)
> (2) The first sheet includes Rev. B and Rev. C information, supposedly

Would you be able to email a copy of the datasheet that covers both NAND01GW3B2B
and NAND01GW3B2C devices?  I have several datasheets for each separately, but
none that covers both.

> (3) The second sheet includes Rev. C only
> (4) The entries you deleted were from the second sheet and probably
> should have been labeled Rev. C, not Rev. B - the datasheet was
> inconsistent.

Yes, that makes sense, and is what I was meant when I suggested it was a "Rev C"
vs "Rev B" issue.  I believe the data corresponds to NAND01GW3B2C rather than
NAND01GW3B2B.  My patch deleted this entry, since a correct NAND01GW3B2B already
existed, and I then suggested adding a correct entry for NAND01GW3B2C.  Perhaps
we just update the patch to rename the incorrect NAND01GW3B2B entry with
NAND01GW3B2C?

> (5) My sample part (ST NAND01GW3B2C) returns proper ONFI signature and
> parameter page
> (6) My sample part (ST NAND01GW3B2C) reads an actual ID that matches
> the string from the NAND01GW3B2B that you are deleting (this is a
> mixup/typo; see comment (4))
> 
> I'm not sure how to reconcile the histories from (1). Perhaps my 1st
> sheet represents *only* Rev. B and the second sheet represents *only*
> Rev. C?

That would be my guess, but anything is possible when it comes to NAND datasheets!

> 
> If my statements aren't clear enough, I'll send a sample patch that
> would 'reconcile' things a bit.
> 
> BTW, what's the ID string from your sample?
> 

My sample returns a READID of 0x20f1001d.  It returns the 'ONFI' signature from
READID to 0x20, but I still fail to get anything back from NAND_CMD_PARAM.  I
suspect it is a bug in my driver somewhere, but I haven't had a chance to look
into it further yet.

> Any thoughts on the ST vs. Numonyx naming? Are they entirely
> interchangeable names for these chips, where you may find similar/same
> parts with different manufacturers slapped on? (seeing as I have an ST
> part that matches a Numonyx data sheet)
> 

Yes, when Numonyx was spun-out from ST, the datasheets were re-branded but the
actual chip packages still used the ST logo, and the ST JEDEC ID (and ST fabs I
believe).  Numonyx has now been brought by Micron, and it seems Micron are only
offering "Numonyx" parts that do not clash with its own portfolio.

Cheers,

Angus

  reply	other threads:[~2011-12-13 14:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 12:07 [PATCH (mtd-www) 01/13] nand-data: update TC58DVM72A1TG00 BBM info Angus CLARK
2011-12-06 12:07 ` [PATCH (mtd-www) 02/13] nand-data: updates to S30ML-P devices Angus CLARK
2011-12-06 12:07   ` [PATCH (mtd-www) 03/13] nand-data: Samsung devices: fix ID Length = "5?" Angus CLARK
2011-12-06 12:07     ` [PATCH (mtd-www) 04/13] nand-data: Fix Numonyx 'NAND02GW42C' name Angus CLARK
2011-12-06 12:07       ` [PATCH (mtd-www) 05/13] nand-data: remove incorrect/duplicate Numonyx NAND01G devices Angus CLARK
2011-12-06 12:07         ` [PATCH (mtd-www) 06/13] nand-data: fix name for Samsung "K9XDG08U5D" Angus CLARK
2011-12-06 12:07           ` [PATCH (mtd-www) 07/13] nand-data: fix data for Numonyx NAND08GW3F2B device Angus CLARK
2011-12-06 12:07             ` [PATCH (mtd-www) 08/13] nand-data: fix ID Length for Hynix "HY27US{08, 16}12(1/2)B" devices Angus CLARK
2011-12-06 12:07               ` [PATCH (mtd-www) 09/13] nand-data: Update BBM info for Toshiba TC58DVG02A5 Angus CLARK
2011-12-06 12:07                 ` [PATCH (mtd-www) 10/13] nand-data: update READID data for family of Micron devices Angus CLARK
2011-12-06 12:07                   ` [PATCH (mtd-www) 11/13] nand-data: update MT29F8G08AB--- device IDs Angus CLARK
2011-12-06 12:07                     ` [PATCH (mtd-www) 12/13] nand-data: add columns to the table Angus CLARK
2011-12-06 12:07                       ` [PATCH (mtd-www) 13/13] nand-data: add devices Angus CLARK
2011-12-07 20:03                 ` [PATCH (mtd-www) 09/13] nand-data: Update BBM info for Toshiba TC58DVG02A5 Brian Norris
2011-12-07 19:52               ` [PATCH (mtd-www) 08/13] nand-data: fix ID Length for Hynix "HY27US{08, 16}12(1/2)B" devices Brian Norris
2011-12-09 11:45                 ` Angus CLARK
2011-12-07 19:43             ` [PATCH (mtd-www) 07/13] nand-data: fix data for Numonyx NAND08GW3F2B device Brian Norris
2011-12-07 19:38           ` [PATCH (mtd-www) 06/13] nand-data: fix name for Samsung "K9XDG08U5D" Brian Norris
2011-12-09 11:38             ` Angus CLARK
2011-12-09 20:49               ` Brian Norris
2011-12-07 19:28         ` [PATCH (mtd-www) 05/13] nand-data: remove incorrect/duplicate Numonyx NAND01G devices Brian Norris
2011-12-09 11:04           ` Angus CLARK
2011-12-09 21:14             ` Brian Norris
2011-12-13 14:24               ` Angus CLARK [this message]
2011-12-07 18:58       ` [PATCH (mtd-www) 04/13] nand-data: Fix Numonyx 'NAND02GW42C' name Brian Norris
2011-12-07 18:55     ` [PATCH (mtd-www) 03/13] nand-data: Samsung devices: fix ID Length = "5?" Brian Norris
2011-12-07 18:49   ` [PATCH (mtd-www) 02/13] nand-data: updates to S30ML-P devices Brian Norris
2011-12-09  8:35     ` Angus CLARK
2011-12-09 20:42       ` Brian Norris
2011-12-06 21:02 ` [PATCH (mtd-www) 01/13] nand-data: update TC58DVM72A1TG00 BBM info Artem Bityutskiy
2011-12-07 18:14   ` Brian Norris
2011-12-08 22:16     ` Artem Bityutskiy
2011-12-08 22:18 ` Artem Bityutskiy

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=4EE7602F.30508@st.com \
    --to=angus.clark@st.com \
    --cc=computersforpeace@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.