m25p80 spi1.0: unrecognized JEDEC id
marex at denx.de
Tue Feb 10 02:55:44 PST 2015
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 at 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?
More information about the linux-mtd