From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Marek Vasut <marex@denx.de>,
linux-mtd@lists.infradead.org,
Kevin Cernekee <cernekee@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 1/1 RFC] mtd: spi-nor: Fix ID for Spansion s70fl01gs
Date: Thu, 06 Nov 2014 08:01:35 +0100 [thread overview]
Message-ID: <1680080.dLpxQOxLtG@ws-stein> (raw)
In-Reply-To: <20141105211334.GV23619@ld-irv-0074>
Hello Brian,
thanks for replying.
On Wednesday 05 November 2014 13:13:34, Brian Norris wrote:
> On Mon, Sep 29, 2014 at 11:43:15AM +0200, Alexander Stein wrote:
> > The Device ID is the same as with s25fl512s as stated in datasheet:
> > 6. Identification (RDID)
> > The Read Identification (RDID) command outputs the one-byte manufacturer
> > identification, followed by the two-byte device identification and the
> > bytes for the Common Flash Interface (CFI) tables. Each die of the FL01GS
> > dual die stack will have identical identification data as the FL512S die,
> > with the exception of the CFI data at byte 27h, as shown in Table 6.1.
> >
> > If DT is configured with 's70fl01gs' I get the following warnings (on a 3.12
> > kernel, but that shouldn't matter):
> > m25p80 spi32766.0: found s25fl512s, expected s70fl01gs
> > m25p80 spi32766.1: found s25fl512s, expected s70fl01gs
> >
> > Signed-off-by: Alexander Stein <alexander.stein@systec-electronic.com>
> > ---
> > I am aware that there is now an ID conflict. But this is due that the
> > s70fl01gs simply uses two separate chips. How to handle that?
>
> Maybe you should just be specifying s25fl512s in your DT instead?
This is what I'm doing now. It seems to me that this is currently the only valid solution.
> Are we sure there are no s70fl01gs devices which use the current ID? I
> know some manufacturers are prone to doing the stupidest things you can
> think of (like arbitrarily-changing IDs).
To quote from http://www.spansion.com/Support/Datasheets/S70FL01GS.pdf:
6. Read Identification (RDID)
The Read Identification (RDID) command outputs the one-byte manufacturer identification, followed by the
two-byte device identification and the bytes for the Common Flash Interface (CFI) tables. Each die of the
FL01GS dual die stack will have identical identification data as the FL512S die, with the exception of the CFI
data at byte 27h, as shown in Table 6.1.
So, AFAICS you can only distinguish two FL512S from a FL01GS by reading this CFI byte which isn't done in linux.
Best regards,
Alexander
--
Dipl.-Inf. Alexander Stein
SYS TEC electronic GmbH
Am Windrad 2
08468 Heinsdorfergrund
Tel.: 03765 38600-1156
Fax: 03765 38600-4100
Email: alexander.stein@systec-electronic.com
Website: www.systec-electronic.com
Managing Director: Dipl.-Phys. Siegmar Schmidt
Commercial registry: Amtsgericht Chemnitz, HRB 28082
next prev parent reply other threads:[~2014-11-06 7:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 9:43 [PATCH 1/1 RFC] mtd: spi-nor: Fix ID for Spansion s70fl01gs Alexander Stein
2014-10-14 6:30 ` Alexander Stein
2014-11-05 21:13 ` Brian Norris
2014-11-06 7:01 ` Alexander Stein [this message]
2014-11-06 7:02 ` Alexander Stein
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=1680080.dLpxQOxLtG@ws-stein \
--to=alexander.stein@systec-electronic.com \
--cc=cernekee@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
/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