* m25p80 spi1.0: unrecognized JEDEC id
@ 2015-02-09 22:09 Fabio Estevam
2015-02-09 22:18 ` Brian Norris
0 siblings, 1 reply; 5+ messages in thread
From: Fabio Estevam @ 2015-02-09 22:09 UTC (permalink / raw)
To: Brian Norris, Marek Vašut; +Cc: Huang Shijie, linux-mtd
Hi,
Running linux-next 20150209 on a mx28evk I see that m25p80 is not
detected correctly:
m25p80 spi1.0: unrecognized JEDEC id bytes: bf, 24, 40
On 3.19 it probes fine though:
m25p80 spi1.0: sst25vf016b (2048 Kbytes)
I can start bisecting it, but just wondering if someone is aware of
this issue or has any ideas.
Thanks,
Fabio Estevam
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: m25p80 spi1.0: unrecognized JEDEC id
2015-02-09 22:09 m25p80 spi1.0: unrecognized JEDEC id Fabio Estevam
@ 2015-02-09 22:18 ` Brian Norris
2015-02-09 23:39 ` Fabio Estevam
0 siblings, 1 reply; 5+ messages in thread
From: Brian Norris @ 2015-02-09 22:18 UTC (permalink / raw)
To: Fabio Estevam; +Cc: Marek Vašut, Huang Shijie, linux-mtd
On Mon, Feb 09, 2015 at 08:09:02PM -0200, Fabio Estevam wrote:
> Hi,
>
> Running linux-next 20150209 on a mx28evk I see that m25p80 is not
> detected correctly:
>
> m25p80 spi1.0: unrecognized JEDEC id bytes: bf, 24, 40
That's not good. I don't see anything in MTD's -next that should cause
that though.
> On 3.19 it probes fine though:
>
> m25p80 spi1.0: sst25vf016b (2048 Kbytes)
>
> I can start bisecting it, but just wondering if someone is aware of
> this issue or has any ideas.
I'm not aware of this. Please keep me updated if you find anything.
Brian
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: m25p80 spi1.0: unrecognized JEDEC id
2015-02-09 22:18 ` Brian Norris
@ 2015-02-09 23:39 ` Fabio Estevam
2015-02-10 10:55 ` Marek Vasut
0 siblings, 1 reply; 5+ messages in thread
From: Fabio Estevam @ 2015-02-09 23:39 UTC (permalink / raw)
To: Brian Norris; +Cc: Marek Vašut, Huang Shijie, linux-mtd
On Mon, Feb 9, 2015 at 8:18 PM, Brian Norris
<computersforpeace@gmail.com> wrote:
> On Mon, Feb 09, 2015 at 08:09:02PM -0200, Fabio Estevam wrote:
>> Hi,
>>
>> Running linux-next 20150209 on a mx28evk I see that m25p80 is not
>> detected correctly:
>>
>> m25p80 spi1.0: unrecognized JEDEC id bytes: bf, 24, 40
>
> That's not good. I don't see anything in MTD's -next that should cause
> that though.
Yes, I have just tested other platform (mx6) with linux-next and
m25p80 can be probed.
Looks like the issue is mxs specific and comes from other area (spi
driver, dma, clocks, etc).
Regards,
Fabio Estevam
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: m25p80 spi1.0: unrecognized JEDEC id
2015-02-09 23:39 ` Fabio Estevam
@ 2015-02-10 10:55 ` Marek Vasut
2015-02-10 12:48 ` Fabio Estevam
0 siblings, 1 reply; 5+ messages in thread
From: Marek Vasut @ 2015-02-10 10:55 UTC (permalink / raw)
To: Fabio Estevam; +Cc: Huang Shijie, Brian Norris, linux-mtd
On Tuesday, February 10, 2015 at 12:39:22 AM, Fabio Estevam wrote:
> On Mon, Feb 9, 2015 at 8:18 PM, Brian Norris
>
> <computersforpeace@gmail.com> wrote:
> > On Mon, Feb 09, 2015 at 08:09:02PM -0200, Fabio Estevam wrote:
> >> Hi,
> >>
> >> Running linux-next 20150209 on a mx28evk I see that m25p80 is not
> >> detected correctly:
> >>
> >> m25p80 spi1.0: unrecognized JEDEC id bytes: bf, 24, 40
> >
> > That's not good. I don't see anything in MTD's -next that should cause
> > that though.
>
> Yes, I have just tested other platform (mx6) with linux-next and
> m25p80 can be probed.
>
> Looks like the issue is mxs specific and comes from other area (spi
> driver, dma, clocks, etc).
Was the clock patch mucking with FRAC0 and FRAC1 merged by any chance?
Best regards,
Marek Vasut
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: m25p80 spi1.0: unrecognized JEDEC id
2015-02-10 10:55 ` Marek Vasut
@ 2015-02-10 12:48 ` Fabio Estevam
0 siblings, 0 replies; 5+ messages in thread
From: Fabio Estevam @ 2015-02-10 12:48 UTC (permalink / raw)
To: Marek Vasut, Stefan Wahren; +Cc: Huang Shijie, Brian Norris, linux-mtd
Hi Marek,
On Tue, Feb 10, 2015 at 8:55 AM, Marek Vasut <marex@denx.de> wrote:
> On Tuesday, February 10, 2015 at 12:39:22 AM, Fabio Estevam wrote:
> Was the clock patch mucking with FRAC0 and FRAC1 merged by any chance?
Thanks for your suggestion! You are right: If I revert Stefan's patch:
commit 039e5970750775f102b255de9bf914e04955c6da ("clk: mxs: Fix
invalid 32-bit access to frac registers")
then the SPI NOR flash is probed correctly on mx28evk.
Stefan,
Could you please take a look?
Thanks,
Fabio Estevam
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-02-10 12:48 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-02-09 22:09 m25p80 spi1.0: unrecognized JEDEC id Fabio Estevam
2015-02-09 22:18 ` Brian Norris
2015-02-09 23:39 ` Fabio Estevam
2015-02-10 10:55 ` Marek Vasut
2015-02-10 12:48 ` Fabio Estevam
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.