public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Angus CLARK <angus.clark@st.com>
To: linux-mtd@lists.infradead.org
Cc: Angus CLARK <angus.clark@st.com>,
	Brian Norris <computersforpeace@gmail.com>
Subject: Re: [PATCH (mtd-www) 5/7] nand-data: add columns to the table
Date: Tue, 10 Jan 2012 11:59:20 +0000	[thread overview]
Message-ID: <4F0C2818.6020208@st.com> (raw)
In-Reply-To: <CAN8TOE_VO29CuL2eAFEmb+xUbhpA1_eiH=podORq5wsYqTZaUA@mail.gmail.com>

Hi Brian,

Thanks for reviewing the patches.

On 01/09/2012 07:38 PM, Brian Norris wrote:
> On Thu, Jan 5, 2012 at 8:13 AM, Angus CLARK <angus.clark@st.com> wrote:
> These patches get a little harder to deal with when there are columns
> added, since line-by-line diff is pretty useless! 

Indeed, 'diff' is not particularly helpful when adding columns.  When re-doing
the patches, I will attach an openoffice (.ods) version of the file, with the
new columns highlighted in red.  This should make it easier to see what
information has been added.  Then, by deleting the red columns, saving as CSV,
and diff'ing with the previous version, we can check no other changes have been
introduced.  What do you think?

> 
> Potential unintended changes:
> 
> * Under the ONFI column, you changed "1.0" to just "1" (on, for
> example, Numonyx NAND04GR3B2). I'm guessing that your CSV editor did
> this automatically, treating it like an integer. 

Yes, I forgot to set the column format!  Hopefully the work-flow mentioned above
will catch this type of error.

> * Scan page 1: you missed Samsung K9XDG08U5D, which should have 'Scan
> Page 1 = FALSE'

Yes, I will correct this in the next version of the patch.

> * CS, LUNs, R/B#: looks good, although I didn't do in-depth review of
> *all* the data sheets :)

It does get a bit tedious!  I also want to add the number of planes at some
point, but this will have to wait a while!

> * I/O I/F: is this an abbreviation for "Input/Output Interfaces"?

Yes, although different manufacturers tend to use different names.  It is used
here to mean the control signals (CL, AL, WE#, RE#) and the data lines (DQ[7:0]
or DQ[15:0]).  Some multi-CS devices share a single interface (typically on TSOP
packages), whereas some use a dual interface (typically BGA packages).

> * Under the "Base Part" column, you have a typo where "M29F2G08AAC"
> should be "MT29F2G08AAC"

Yes, I will correct this in the next version of the patch.

> * When you list "NAND04G-B2D" in the "Base Part" column, can you
> either use the lowercase "x" for a wildcard as we discussed or just
> state the exact chip name when possible?

I will use the exact chip name -- I should have used this in the first place!

> Overall, I've been a little fuzzy on how various multi-LUN
> configurations are handled; mostly, I deal with single-CS chips, but I
> thought I was getting the hang of how multiple LUNs were introduced
> via the CS and R/B pins. However, I see that there are occasionally
> multi-LUN chips where `Num. LUNs > Num. CS'. Apparently, there are
> multiple LUNs on the same CE# and R/B# lines. Are such LUNs handled
> transparently, such that no special board wiring is needed and that
> software doesn't notice a difference? And is this where multi-plane
> operations come into the picture?

Yes, a device that comprises two LUNs on a single CS will handle the routing
internally, based on upper address bit(s).  Typically, the device will also
support multi-LUN, interleaved, operations.  (This is different to multi-plane
support though.)

> Similarly, I'm not sure of the exact meaning of I/O I/F (as asked
> above). I see that it is delineated in some datasheets as "number of
> I/O", but it's not clearly defined.
> 

The Micron datasheets give some nice diagrams, see MT29F64G08CBAAA for example
(p20-25 on my Rev. E version).  This is a good example to look at, since the
family of devices support multi-LUN and multi-plane operations.

I did this little ascii diagram a while ago, but the Micron ones are probably
better:

           --------------------------------------------------------------
           |   Device (Package)                                         |
           |                                                            |
           |    ----------------------------------------------------    |
           |    | Chip 0 (Target 0)                                |    |
    CE0# --|--->|                                                  |    |
           |    |  ---------------------    ---------------------  |    |
           |    |  | LUN 0 (Die 0)     |    | LUN 1 (Die 1)     |  |    |
           |    |  |         |         |    |         |         |  |    |
           |    |  |         |         |    |         |         |  |    |
           |    |  | Plane 0 | Plane 1 |    | Plane 0 | Plane 1 |  |    |
           |    |  ---------------------    ---------------------  |    |
           |    |                                                  |    |
           |    ----------------------------------------------------    |
           |                                                            |
           |    ----------------------------------------------------    |
           |    | Chip 1 (Target 1)                                |    |
    CE1# --|--->|                                                  |    |
           |    |  ---------------------    ---------------------  |    |
           |    |  | LUN 0 (Die 0)     |    | LUN 1 (Die 1)     |  |    |
           |    |  |         |         |    |         |         |  |    |
           |    |  |         |         |    |         |         |  |    |
           |    |  | Plane 0 | Plane 1 |    | Plane 0 | Plane 1 |  |    |
           |    |  ---------------------    ---------------------  |    |
           |    |                                                  |    |
           |    ----------------------------------------------------    |
           |                                                            |
           --------------------------------------------------------------


Cheers,

Angus

  reply	other threads:[~2012-01-10 11:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 16:13 [PATCH (mtd-www) 1/7] nand-data: updates to S30ML-P devices Angus CLARK
2012-01-05 16:13 ` [PATCH (mtd-www) 2/7] nand-data: rename duplicate Numonyx NAND01G devices as 'Rev C' Angus CLARK
2012-01-07  3:14   ` Brian Norris
2012-01-05 16:13 ` [PATCH (mtd-www) 3/7] nand-data: update READID data for family of Micron devices Angus CLARK
2012-01-07  3:21   ` Brian Norris
2012-01-05 16:13 ` [PATCH (mtd-www) 4/7] nand-data: update MT29F8G08AB--- device IDs Angus CLARK
2012-01-07  3:26   ` Brian Norris
2012-01-05 16:13 ` [PATCH (mtd-www) 5/7] nand-data: add columns to the table Angus CLARK
2012-01-09 19:38   ` Brian Norris
2012-01-10 11:59     ` Angus CLARK [this message]
2012-01-13 21:35       ` Brian Norris
2012-01-05 16:13 ` [PATCH (mtd-www) 6/7] nand-data: expand Samsung "K9XDG08U5D" devices Angus CLARK
2012-01-09 19:43   ` Brian Norris
2012-01-05 16:14 ` [PATCH (mtd-www) 7/7] nand-data: add devices Angus CLARK
2012-01-07  3:06 ` [PATCH (mtd-www) 1/7] nand-data: updates to S30ML-P devices Brian Norris
2012-01-07 15:14 ` 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=4F0C2818.6020208@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox