From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Roger Quadros <rogerq@ti.com>
Cc: tony@atomide.com, bcousson@baylibre.com, balbi@ti.com, nm@ti.com,
linux-omap@vger.kernel.org, linux-usb@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: omap3-beagle: Fix USB host on beagle boards (for 3.13)
Date: Tue, 03 Dec 2013 12:10:17 +0100 [thread overview]
Message-ID: <5279201.QqSaKtdayD@avalon> (raw)
In-Reply-To: <529DA639.8000905@ti.com>
Hi Roger,
On Tuesday 03 December 2013 11:36:57 Roger Quadros wrote:
> On 12/03/2013 05:54 AM, Laurent Pinchart wrote:
> > Hi Roger,
> >
> > On Monday 25 November 2013 15:55:45 Roger Quadros wrote:
> >> Beagle (rev. C4) and Beagle-XM (all revs) need VAUX2 1.8V supply
> >> for the USB PHY.
> >>
> >> As the generic PHY driver can't handle more than one supply
> >> at the moment, we configure this supply to be always on.
> >> This will cause a very small power impact if the USB host subsystem
> >> is not in use, about 76.86 micro-W + LDO power.
> >>
> >> Older Beagle boards (prior to C4) don't have VAUX2 connected anywhere,
> >> so there won't be any functional impact on those boards other than
> >> some additional LDO power consumption.
> >
> > Do I need any patch other than this one (on top of v3.13-rc1) to enable
> > the ethernet port on a Beagleboard-xM rev B ? Here's what the kernel
> > reports at boot (with ignore_loglevel set on the command line).
>
> It seems on Rev A/B, the power enable line for the USB hub has reversed
> polarity than Rev C.
>
> Does the below patch work for you?
It does, thank you.
> If yes, how do we account for it? Do we add a new file
> "omap3-beagle-xm-ab.dts" for rev A/B boards?
Unless we want to add board code back with a runtime check, which I doubt
would be regarded as a good idea, I don't see any other easy solution.
> diff --git a/arch/arm/boot/dts/omap3-beagle-xm.dts
> b/arch/arm/boot/dts/omap3-beagle-xm.dts index b39918e..434d903 100644
> --- a/arch/arm/boot/dts/omap3-beagle-xm.dts
> +++ b/arch/arm/boot/dts/omap3-beagle-xm.dts
> @@ -78,6 +78,7 @@
> regulator-max-microvolt = <3300000>;
> gpio = <&twl_gpio 18 0>; /* GPIO LEDA */
> startup-delay-us = <70000>;
> + enable-active-high;
> };
>
> /* HS USB Host PHY on PORT 2 */
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2013-12-03 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 13:55 [PATCH] ARM: dts: omap3-beagle: Fix USB host on beagle boards (for 3.13) Roger Quadros
[not found] ` <1385387745-7162-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2013-11-25 15:50 ` Nishanth Menon
[not found] ` <CAGo_u6ryFJvBwd=S9A-nJw+eoGguPj0jMOtgMiZ7mXXAbh4i+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-11-26 8:56 ` Roger Quadros
2013-11-26 22:27 ` Tony Lindgren
2013-12-03 3:54 ` Laurent Pinchart
2013-12-03 9:36 ` Roger Quadros
2013-12-03 11:10 ` Laurent Pinchart [this message]
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=5279201.QqSaKtdayD@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=balbi@ti.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=nm@ti.com \
--cc=rogerq@ti.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).