From: Marek Vasut <marex@denx.de>
To: Chunhe Lan <Chunhe.Lan@freescale.com>
Cc: Huang Shijie <shijie8@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: spi-nor: Move n25q032 entry to Micron devices list
Date: Wed, 29 Oct 2014 15:05:48 +0100 [thread overview]
Message-ID: <201410291505.48720.marex@denx.de> (raw)
In-Reply-To: <1414576675-7792-1-git-send-email-Chunhe.Lan@freescale.com>
On Wednesday, October 29, 2014 at 10:57:55 AM, Chunhe Lan wrote:
[...]
There are problems with this patch. Firstly, it misses any description
explaining why the change took place at all. From an outside observer
point of view, this change seems random at best.
Secondly, the change in itself makes no sense -- it just reorders the
entries in an array. I can only speculate here, that your SPI NOR was
recognised as some other part, right ? That's why moving the n25q032
higher resolved the problem for you, right ?
The problem is with the fragility of this code which matches the JEDEC
ID and type of the SPI NOR. I recall Huang had some patches which tried
to resolve this, not sure what the status of those patches is though.
> Signed-off-by: Chunhe Lan <Chunhe.Lan@freescale.com>
> Cc: Brian Norris <computersforpeace@gmail.com>
> Cc: Marek Vasut <marex@denx.de>
> Cc: Huang Shijie <shijie8@gmail.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 ae16aa2..1fa5e05 100644
> --- a/drivers/mtd/spi-nor/spi-nor.c
> +++ b/drivers/mtd/spi-nor/spi-nor.c
> @@ -530,6 +530,7 @@ const struct spi_device_id spi_nor_ids[] = {
> { "mx66l1g55g", INFO(0xc2261b, 0, 64 * 1024, 2048, SPI_NOR_QUAD_READ)
},
>
> /* Micron */
> + { "n25q032", INFO(0x20ba16, 0, 64 * 1024, 64, 0) },
> { "n25q064", INFO(0x20ba17, 0, 64 * 1024, 128, 0) },
> { "n25q128a11", INFO(0x20bb18, 0, 64 * 1024, 256, 0) },
> { "n25q128a13", INFO(0x20ba18, 0, 64 * 1024, 256, 0) },
> @@ -586,7 +587,6 @@ const struct spi_device_id spi_nor_ids[] = {
> { "m25p32", INFO(0x202016, 0, 64 * 1024, 64, 0) },
> { "m25p64", INFO(0x202017, 0, 64 * 1024, 128, 0) },
> { "m25p128", INFO(0x202018, 0, 256 * 1024, 64, 0) },
> - { "n25q032", INFO(0x20ba16, 0, 64 * 1024, 64, 0) },
>
> { "m25p05-nonjedec", INFO(0, 0, 32 * 1024, 2, 0) },
> { "m25p10-nonjedec", INFO(0, 0, 32 * 1024, 4, 0) },
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-10-29 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 9:57 [PATCH] mtd: spi-nor: Move n25q032 entry to Micron devices list Chunhe Lan
2014-10-29 14:05 ` Marek Vasut [this message]
2014-10-29 17:40 ` Rafał Miłecki
2014-10-29 19:19 ` Marek Vasut
2014-10-29 19:43 ` Rafał Miłecki
2014-10-29 19:54 ` Marek Vasut
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=201410291505.48720.marex@denx.de \
--to=marex@denx.de \
--cc=Chunhe.Lan@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=shijie8@gmail.com \
/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