From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd/m25p80: add device tree probe support
Date: Mon, 25 Jun 2012 18:50:10 +0200 [thread overview]
Message-ID: <201206251850.10839.marex@denx.de> (raw)
In-Reply-To: <20120625161506.GH2342@S2101-09.ap.freescale.net>
Dear Shawn Guo,
> On Mon, Jun 25, 2012 at 06:01:22PM +0200, Marek Vasut wrote:
> > Dear Shawn Guo,
> >
> > > On Sat, Jun 23, 2012 at 04:15:18AM +0200, Marek Vasut wrote:
> > > > So is there any particular reason why this wasn't applied?
> > >
> > > Let me remind Artem by resending the patch tomorrow.
> >
> > Actually ... the SPI does have the heuristics to probe this chip without
> > the patch. But there was this discussion about them eventually being
> > removed. That was a point raised by you I think. Is that still valid?
>
> That was a point raised by Grant. IIRC, the reason I made the patch
> is my system does not probe the device without the patch. I can
> retest, and if it's true that the patch is not necessarily needed,
> I will probably let it be.
116 ssp2: ssp at 80014000 {
117 #address-cells = <1>;
118 #size-cells = <0>;
119 compatible = "fsl,imx28-spi";
120 pinctrl-names = "default";
121 pinctrl-0 = <&spi2_pins_a>;
122 status = "okay";
123
124 flash: m25p80 at 0 {
125 #address-cells = <1>;
126 #size-cells = <1>;
127 compatible = "m25p80";
128 spi-max-frequency = <25000000>;
129 reg = <0>;
130 };
131 };
I use this + my SPI patches I submitted recently.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-06-25 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 13:37 [PATCH] mtd/m25p80: add device tree probe support Shawn Guo
2011-07-25 21:19 ` Grant Likely
2011-07-28 19:22 ` manu
2011-07-28 21:45 ` Grant Likely
2012-06-23 2:15 ` Marek Vasut
2012-06-25 15:40 ` Shawn Guo
2012-06-25 16:01 ` Marek Vasut
2012-06-25 16:15 ` Shawn Guo
2012-06-25 16:50 ` Marek Vasut [this message]
2012-06-26 8:15 ` Shawn Guo
2012-06-26 11:47 ` 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=201206251850.10839.marex@denx.de \
--to=marex@denx.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).