From: Marek Vasut <marex@denx.de>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Priyanka Jain <Priyanka.Jain@freescale.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Subject: Re: [PATCH] mtd: m25p80: Add support for Micron N25Q512A memory
Date: Wed, 2 Oct 2013 22:55:01 +0200 [thread overview]
Message-ID: <201310022255.01344.marex@denx.de> (raw)
In-Reply-To: <CAN8TOE8ii_fbz77M4HJBvyWwPxe+AGOh-sZW=rrwEKfxGhr61g@mail.gmail.com>
Dear Brian Norris,
> On Wed, Oct 2, 2013 at 1:02 PM, Marek Vasut <marex@denx.de> wrote:
> > Hi Brian,
> >
> >> + Marek for real!
> >>
> >> On Wed, Oct 2, 2013 at 11:51 AM, Brian Norris
> >>
> >> <computersforpeace@gmail.com> wrote:
> >> > + Marek
> >> >
> >> > On Wed, Sep 04, 2013 at 10:16:56AM +0530, Priyanka Jain wrote:
> >> >> Micron N25Q512A is a spi flash memory with following features:
> >> >> -64MB size, 1.8V, Mulitple I/O, 4KB Sector erase memory.
> >> >> -Memory is organised as 1024(64KB) main sectors.
> >> >> -Each sector is divided into 256 pages.
> >> >> -Register set/Opcodes are similar to other N25Q family products.
> >> >>
> >> >> Signed-off-by: Priyanka Jain <Priyanka.Jain@freescale.com>
> >> >> ---
> >> >>
> >> >> drivers/mtd/devices/m25p80.c | 1 +
> >> >> 1 files changed, 1 insertions(+), 0 deletions(-)
> >> >>
> >> >> diff --git a/drivers/mtd/devices/m25p80.c
> >> >> b/drivers/mtd/devices/m25p80.c index 26b14f9..94e3b53 100644
> >> >> --- a/drivers/mtd/devices/m25p80.c
> >> >> +++ b/drivers/mtd/devices/m25p80.c
> >> >> @@ -774,6 +774,7 @@ static const struct spi_device_id m25p_ids[] = {
> >> >>
> >> >> { "n25q128a11", INFO(0x20bb18, 0, 64 * 1024, 256, 0) },
> >> >> { "n25q128a13", INFO(0x20ba18, 0, 64 * 1024, 256, 0) },
> >> >> { "n25q256a", INFO(0x20ba19, 0, 64 * 1024, 512, SECT_4K) },
> >> >>
> >> >> + { "n25q512a", INFO(0x20bb20, 0, 64 * 1024, 512, SECT_4K) },
> >
> > Why does this n25q256a and n25q512a have exactly the same geometry? I
> > mean, those chips differ in size, do they not ? ;-)
> >
> >> > This device actually has the same ID as Micron's next line
> >> > (MT25QL512A). They have the same geometry, so maybe that's not a
> >> > problem.
>
> I was referring to Micron n25q512a (which this patch mentions) and
> Micron's new generation of flash MT25QL512A (not mentioned in the
> original code or patch). They are different flash and are named
> differently but have the same ID. Perhaps my usage of the word "line"
> was confusing.
Yes I know. Still, that n25q512a line being the exact copy of n25q256a doesn't
seem right.
The new ql512a seems line just a compatible replacement part for older lineup.
Happens all the time.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-10-02 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 4:46 [PATCH] mtd: m25p80: Add support for Micron N25Q512A memory Priyanka Jain
2013-10-02 18:51 ` Brian Norris
2013-10-02 18:55 ` Brian Norris
2013-10-02 20:02 ` Marek Vasut
2013-10-02 20:11 ` Brian Norris
2013-10-02 20:55 ` Marek Vasut [this message]
2013-10-02 21:01 ` Brian Norris
2013-10-15 4:32 ` Jain Priyanka-B32167
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=201310022255.01344.marex@denx.de \
--to=marex@denx.de \
--cc=Priyanka.Jain@freescale.com \
--cc=artem.bityutskiy@linux.intel.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