public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Priyanka Jain <Priyanka.Jain@freescale.com>,
	MTD Maling List <linux-mtd@lists.infradead.org>,
	linux-spi <linux-spi@vger.kernel.org>
Subject: Re: [PATCH] mtd: spi-nor: Correct device-id for n25q512a device
Date: Tue, 29 Jul 2014 21:14:31 -0700	[thread overview]
Message-ID: <20140730041431.GD11952@brian-ubuntu> (raw)
In-Reply-To: <CAMuHMdV52qwThCezu=4NCpVBwbM2AjSK4cKXA+BdO=v_Yy2sBQ@mail.gmail.com>

Hi Priyanka,

On Tue, Jul 08, 2014 at 09:38:19AM +0200, Geert Uytterhoeven wrote:
> CC linux-mtd

(Thanks for forwarding, Geert)

> On Tue, Jul 8, 2014 at 6:54 AM, Priyanka Jain
> <Priyanka.Jain@freescale.com> wrote:
> > Signed-off-by: Priyanka Jain <Priyanka.Jain@freescale.com>
> > ---
> >  drivers/mtd/spi-nor/spi-nor.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
> > index c713c86..148bb51d 100644
> > --- a/drivers/mtd/spi-nor/spi-nor.c
> > +++ b/drivers/mtd/spi-nor/spi-nor.c
> > @@ -487,7 +487,7 @@ const struct spi_device_id spi_nor_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, 1024, SECT_4K) },
> > +       { "n25q512a",    INFO(0x20ba20, 0, 64 * 1024, 1024, SECT_4K) },

We can't just change the ID, as this would break other devices.
Apparently there are multiple similar devices with at least two
different IDs. And we already have this patch queued up in l2-mtd.git
(also in linux-next):

commit c14deddec1fbd8c9757c53a49dbfd2dc83265f21
Author: grmoore@altera.com <grmoore@altera.com>
Date:   Tue Apr 29 10:29:51 2014 -0500

    mtd: spi-nor: add support for flag status register on Micron chips

Feel free to test!

> >
> >         /* PMC */
> >         { "pm25lv512",   INFO(0,        0, 32 * 1024,    2, SECT_4K_PMC) },

Brian

  reply	other threads:[~2014-07-30  4:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1404795285-2929-1-git-send-email-Priyanka.Jain@freescale.com>
2014-07-08  7:38 ` [PATCH] mtd: spi-nor: Correct device-id for n25q512a device Geert Uytterhoeven
2014-07-30  4:14   ` Brian Norris [this message]
2014-07-30  4:17     ` Priyanka Jain
2014-07-30  4:26       ` 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=20140730041431.GD11952@brian-ubuntu \
    --to=computersforpeace@gmail.com \
    --cc=Priyanka.Jain@freescale.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.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