From: Marek Vasut <marex@denx.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Huang Shijie <b32955@freescale.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Shawn Guo <shawn.guo@freescale.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Wrong SPI NOR model detected by mx6sl
Date: Thu, 10 Apr 2014 18:07:48 +0200 [thread overview]
Message-ID: <201404101807.48238.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5DR00ea=zfr+eM0uh2L5a6QB93g8X48JNkXZZc4UavdZA@mail.gmail.com>
On Thursday, April 10, 2014 at 05:49:18 PM, Fabio Estevam wrote:
> Hi,
>
> On the imx6sl-evk there is a m25p32 spi nor flash, but in the kernel
> probe we get:
>
> m25p80 spi0.0: found mr25h256, expected m25p32
> m25p80 spi0.0: mr25h256 (32 Kbytes)
>
> On the mx6qsabresd there is also a m25p32, which is correctly detected:
> m25p80 spi0.0: m25p32 (4096 Kbytes)
>
> Any ideas as to why mx6sl detects the wrong spi nor model?
Can you share the JEDEC ID codes that both of the boards actually read from the
SPI NOR ? You can dump those in the m25p80.c driver . That'd be helpful, I
suspect some kind of an "offset" or "polarity inversion" in the SPI
communication causing this.
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: Wrong SPI NOR model detected by mx6sl
Date: Thu, 10 Apr 2014 18:07:48 +0200 [thread overview]
Message-ID: <201404101807.48238.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5DR00ea=zfr+eM0uh2L5a6QB93g8X48JNkXZZc4UavdZA@mail.gmail.com>
On Thursday, April 10, 2014 at 05:49:18 PM, Fabio Estevam wrote:
> Hi,
>
> On the imx6sl-evk there is a m25p32 spi nor flash, but in the kernel
> probe we get:
>
> m25p80 spi0.0: found mr25h256, expected m25p32
> m25p80 spi0.0: mr25h256 (32 Kbytes)
>
> On the mx6qsabresd there is also a m25p32, which is correctly detected:
> m25p80 spi0.0: m25p32 (4096 Kbytes)
>
> Any ideas as to why mx6sl detects the wrong spi nor model?
Can you share the JEDEC ID codes that both of the boards actually read from the
SPI NOR ? You can dump those in the m25p80.c driver . That'd be helpful, I
suspect some kind of an "offset" or "polarity inversion" in the SPI
communication causing this.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-04-10 16:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 15:49 Wrong SPI NOR model detected by mx6sl Fabio Estevam
2014-04-10 15:49 ` Fabio Estevam
2014-04-10 16:07 ` Marek Vasut [this message]
2014-04-10 16:07 ` Marek Vasut
2014-04-10 17:16 ` Fabio Estevam
2014-04-10 17:16 ` Fabio Estevam
2014-04-11 0:26 ` Huang Shijie
2014-04-11 0:26 ` Huang Shijie
2014-04-11 2:09 ` Fabio Estevam
2014-04-11 2:09 ` Fabio Estevam
2014-04-11 11:43 ` Fabio Estevam
2014-04-11 11:43 ` Fabio Estevam
2014-04-11 11:59 ` Marek Vasut
2014-04-11 11:59 ` Marek Vasut
2014-04-11 12:11 ` Fabio Estevam
2014-04-11 12:11 ` Fabio Estevam
2014-04-11 12:16 ` Marek Vasut
2014-04-11 12:16 ` 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=201404101807.48238.marex@denx.de \
--to=marex@denx.de \
--cc=b32955@freescale.com \
--cc=festevam@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=shawn.guo@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.