linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <martinez.javier@gmail.com>
To: Benoit Cousson <b-cousson@ti.com>
Cc: Jon Hunter <jon-hunter@ti.com>, Tony Lindgren <tony@atomide.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: 4430sdp nfsroot broken with ff5c9059
Date: Thu, 11 Apr 2013 11:58:24 +0200	[thread overview]
Message-ID: <CAAwP0s3fjTTFTmAdQ3Ru=gECob0-Vinvs4TLQbcb2eZFb+nXWA@mail.gmail.com> (raw)
In-Reply-To: <516680C5.9040505@ti.com>

On Thu, Apr 11, 2013 at 11:22 AM, Benoit Cousson <b-cousson@ti.com> wrote:
> Hi Javier,
>
> On 04/11/2013 01:58 AM, 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.
>
> It is not really a hack. There is a regulator controlled by a GPIO that
> can control the Ethernet chip power. Both gpio48 and gpio34 are used for
> Ethernet. On some SDP version there is even a third line, but I was not
> able to find any evidence in the schematic I was using.
>
> Regards,
> Benoit
>

Hi Benoit,

I (wrongly) assumed that this was made just to bypass the fact that
neither the ks881 driver nor the DT core call omap_gpio_request() to
enable the GPIO bank module.

But now thanks to your explanation I understand that gpio48 is also
necessary to control the regulator and as Jon said the lucky fact is
that both GPIO 48 and 34 are from the same GPIO bank module (gpio2).
If that was not the case, this would probably not work.

I should learn to not comment without looking at the schematic first.

Thanks a lot and best regards,
Javier

  reply	other threads:[~2013-04-11  9:58 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
2013-04-11  0:50       ` Javier Martinez Canillas
2013-04-11  9:22     ` Benoit Cousson
2013-04-11  9:58       ` Javier Martinez Canillas [this message]
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='CAAwP0s3fjTTFTmAdQ3Ru=gECob0-Vinvs4TLQbcb2eZFb+nXWA@mail.gmail.com' \
    --to=martinez.javier@gmail.com \
    --cc=b-cousson@ti.com \
    --cc=jon-hunter@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --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).