From: Marek Vasut <marex@denx.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: Huang Shijie <shijie8@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: m25p80 spi1.0: unrecognized JEDEC id
Date: Tue, 10 Feb 2015 11:55:44 +0100 [thread overview]
Message-ID: <201502101155.44137.marex@denx.de> (raw)
In-Reply-To: <CAOMZO5BMrA1HGXXoriwbAk53Kmkr8GcQbEt75CuT_voeqW3s6Q@mail.gmail.com>
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
next prev parent reply other threads:[~2015-02-10 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2015-02-10 12:48 ` Fabio Estevam
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=201502101155.44137.marex@denx.de \
--to=marex@denx.de \
--cc=computersforpeace@gmail.com \
--cc=festevam@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