From: Jon Hunter <jon-hunter@ti.com>
To: Javier Martinez Canillas <martinez.javier@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Cousson, Benoit" <b-cousson@ti.com>
Subject: Re: 4430sdp nfsroot broken with ff5c9059
Date: Wed, 10 Apr 2013 19:28:41 -0500 [thread overview]
Message-ID: <516603B9.4080308@ti.com> (raw)
In-Reply-To: <CAAwP0s395mo58b0Wf5mb7TUS8Jske-RWQMKHV2e5KEGNOXZHDw@mail.gmail.com>
On 04/10/2013 06:58 PM, Javier Martinez Canillas wrote:
> On Wed, Apr 10, 2013 at 7:31 PM, Jon Hunter <jon-hunter@ti.com> wrote:
>> Hi Tony,
>>
>> On 04/09/2013 04:23 PM, Tony Lindgren wrote:
>>> Hi Jon,
>>>
>>> Looks like at least 4430sdp nfsroot got broken with commit
>>> ff5c9059 (ARM: dts: OMAP3+: Correct gpio #interrupts-cells
>>> property).
>>
>> Thanks for reporting. I am actually amazed that ethernet is
>> working on any OMAP board (with device-tree) that requires a
>> gpio as an interrupt because we have still not come to an
>> agreement on [1]. Looking at the OMAP4 SDP I believe this is
>> working by luck because there are other gpios in the same
>> bank that are active and so the bank is enabled. If that were
>> not the case then this would not work.
>>
>
> Hi Jon,
>
> Ethernet is working on 4430sdp since the optional "gpio" property is
> specified on the fixed regulator used by the eth device node.
>
> From arch/arm/boot/dts/omap4-sdp.dts:
>
> vdd_eth: fixedregulator-vdd-eth {
> compatible = "regulator-fixed";
> regulator-name = "VDD_ETH";
> regulator-min-microvolt = <3300000>;
> regulator-max-microvolt = <3300000>;
> gpio = <&gpio2 16 0>; /* gpio line 48 */
> enable-active-high;
> regulator-boot-on;
> };
> ...
> &mcspi1 {
> eth@0 {
> compatible = "ks8851";
> spi-max-frequency = <24000000>;
> reg = <0>;
> interrupt-parent = <&gpio2>;
> interrupts = <2>; /* gpio line 34 */
> vdd-supply = <&vdd_eth>;
> };
> };
>
> So is the regulator who is calling gpio_request() and enabling the
> GPIO bank and no the ks881 ethernet driver. That's why it was working
> although I think is just a DT hack and should be changed once we found
> a proper solution to fhis.
Right, in the above I mentioned it is working because of other gpios in
the bank that are enabled. So I understand why it works, but wanted to
point out that this is lucky :-)
Jon
next prev parent reply other threads:[~2013-04-11 0:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 21:23 4430sdp nfsroot broken with ff5c9059 Tony Lindgren
2013-04-10 17:31 ` Jon Hunter
2013-04-10 18:20 ` Tony Lindgren
2013-04-10 20:43 ` Jon Hunter
2013-04-10 20:54 ` Tony Lindgren
2013-04-10 22:25 ` Jon Hunter
2013-04-10 22:27 ` Tony Lindgren
2013-04-13 0:06 ` Tony Lindgren
2013-04-13 2:17 ` Jon Hunter
2013-04-13 16:50 ` Tony Lindgren
2013-04-15 16:57 ` Jon Hunter
2013-04-15 18:10 ` Jon Hunter
2013-04-15 21:27 ` Tony Lindgren
2013-04-16 17:14 ` Jon Hunter
2013-04-16 18:06 ` Tony Lindgren
2013-04-16 18:40 ` Jon Hunter
2013-04-17 0:56 ` Tony Lindgren
2013-04-10 23:58 ` Javier Martinez Canillas
2013-04-11 0:28 ` Jon Hunter [this message]
2013-04-11 0:50 ` Javier Martinez Canillas
2013-04-11 9:22 ` Benoit Cousson
2013-04-11 9:58 ` Javier Martinez Canillas
2013-05-08 22:05 ` Tony Lindgren
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=516603B9.4080308@ti.com \
--to=jon-hunter@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=martinez.javier@gmail.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).