From: Tony Lindgren <tony@atomide.com>
To: Roger Quadros <rogerq@ti.com>
Cc: benoit.cousson@linaro.org, linux-omap@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "Balbi, Felipe" <balbi@ti.com>
Subject: Re: [PATCH v2 4/4] ARM: OMAP2+: Provide alias to USB PHY clock
Date: Tue, 16 Jul 2013 05:32:56 -0700 [thread overview]
Message-ID: <20130716123256.GY7656@atomide.com> (raw)
In-Reply-To: <51E40199.9070906@ti.com>
* Roger Quadros <rogerq@ti.com> [130715 07:11]:
> Hi Tony,
>
> On 06/18/2013 07:04 PM, Roger Quadros wrote:
> > Till the OMAP clocks are correctly defined in device tree, use
> > this temporary hack to provide clock alias to the USB PHY clocks.
> >
> > Without this, USB Host & Ethernet will not be functional with
> > device tree boots on Panda and uEVM.
>
> Looks like this one got missed out.
>
> USB host no longer works on Panda with DT boot.
> Could you please queue this for next 3.11-rc? Thanks.
OK thanks for checking, applying into omap-for-v3.11/fixes.
Looks like I also have some pending the .dts changes in
omap-for-v3.11/dt branch:
4cf2198b1e3cee47a1cccbb500b67782c36615d5 ARM: dts: omap3-beagle-xm: Add USB host supprot for Rev. Ax/Bx
9bc44515819a00c0ffaf751ad497ddf275089ede ARM: dts: omap3-beagle-xm: Add USB Host support
fd65d7df4598c1d2ad27d664c719611a1a070edc ARM: dts: omap3-beagle: Make USB host pin naming consistent
39ea891d9da6ae1824bc9f689db3f306f5ce0724 ARM: dts: omap4-panda: Add USB Host support
Those should get merged as fixes, right? Can you please
check and see if they're still OK or if we also need
something else?
Regards,
Tony
next prev parent reply other threads:[~2013-07-16 12:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 16:04 [PATCH v2 0/4] ARM: OMAP2+: Panda USB Host support and DVI EDID fix Roger Quadros
[not found] ` <1371571487-14389-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2013-06-18 16:04 ` [PATCH v2 1/4] ARM: dts: omap4-panda: Add USB Host support Roger Quadros
2013-06-19 1:17 ` Benoit Cousson
2013-06-19 7:36 ` Roger Quadros
2013-06-19 7:46 ` Tony Lindgren
2013-06-19 10:10 ` Benoit Cousson
2013-06-19 11:03 ` Roger Quadros
2013-06-19 11:30 ` Benoit Cousson
2013-06-19 14:02 ` Roger Quadros
2013-06-19 12:05 ` Florian Vaussard
2013-06-19 12:23 ` Benoit Cousson
2013-06-19 12:32 ` Tony Lindgren
2013-06-19 14:05 ` Roger Quadros
[not found] ` <51C1BA8C.6000703-l0cyMroinI0@public.gmane.org>
2013-06-19 18:17 ` Benoit Cousson
2013-06-19 22:40 ` Benoit Cousson
2013-06-20 11:49 ` Roger Quadros
2013-06-19 12:27 ` Tony Lindgren
2013-06-19 12:34 ` Benoit Cousson
2013-06-19 12:44 ` Tony Lindgren
2013-06-18 16:04 ` [PATCH v2 2/4] ARM: dts: omap4-panda: Fix DVI EDID reads Roger Quadros
2013-06-18 16:04 ` [PATCH v2 3/4] ARM: dts: omap5-uevm: Provide USB Host PHY clock frequency Roger Quadros
2013-06-18 16:04 ` [PATCH v2 4/4] ARM: OMAP2+: Provide alias to USB PHY clock Roger Quadros
2013-07-15 14:05 ` Roger Quadros
2013-07-16 12:32 ` Tony Lindgren [this message]
2013-07-16 13:39 ` Roger Quadros
2013-07-16 13:43 ` Tony Lindgren
2013-07-16 13:12 ` Arend van Spriel
2013-07-16 13:18 ` Arend van Spriel
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=20130716123256.GY7656@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=benoit.cousson@linaro.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=rogerq@ti.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).