From: Tony Lindgren <tony@atomide.com>
To: Roger Quadros <rogerq@ti.com>
Cc: b-cousson@ti.com, nm@ti.com, paul@pwsan.com,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, "B, Ravi" <ravibabu@ti.com>
Subject: Re: [PATCH v3 0/4] ARM: dts: Add USB host support for Panda and Beagle-xm
Date: Thu, 25 Apr 2013 08:34:17 -0700 [thread overview]
Message-ID: <20130425153417.GI5184@atomide.com> (raw)
In-Reply-To: <5174E27B.5090808@ti.com>
* Roger Quadros <rogerq@ti.com> [130422 00:15]:
> On 04/19/2013 06:43 PM, Tony Lindgren wrote:
> > * Roger Quadros <rogerq@ti.com> [130419 03:02]:
> >> Hi Benoit/Tony
> >>
> >> I've consolidated all the USB host device tree patches for Panda and Beagles
> >> to one place and addressed Tony's comments.
> >>
> >> NOTE: patch 1 depends on OMAP clock binding introduced in
> >> https://lkml.org/lkml/2013/4/12/407
> >>
> >> v3:
> >> - updated mux mode to use pulldowns on panda as non-DT boot uses pulldowns.
> >> - fixed usb pin naming for panda, beagle and beagle-xm
> >
> > Cool. Sounds like we should be able to make omap4 DT only for v3.11
>
> when we say DT only for 3.11, does this mean getting rid of hwmod dependency?
That too, but mostly getting rid of the board-*.c files and platform data
init for omap4 :) So a saving of about 5000 lines of code and data
with the legacy mux data dropped. I have some patches to do that but have
not yet posted them as we need to get the boards working well enough
with DT first.
> > then. For that we also need USB on 4430-sdp working, but it now
> > does:
> >
> > ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> > ehci-omap 4a064c00.ehci: failed to get phys phandle in /ocp/usbhshost@4a064000/ehci@4a064c00 node
> > ehci-omap 4a064c00.ehci: failed to get phys phandle in /ocp/usbhshost@4a064000/ehci@4a064c00 node
> > ...
>
> 4430-sdp (Blaze) does not have EHCI USB Host port. It should be using the
> MUSB OTG port.
> >
> > As I have mine in a rack I don't have anything plugged into the
> > USB port there though, but sounds like the phy is not initialized?
> >
>
> +Ravi B.
> He might have some clues.
Yes please check.
Regards,
Tony
next prev parent reply other threads:[~2013-04-25 15:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 9:57 [PATCH v3 0/4] ARM: dts: Add USB host support for Panda and Beagle-xm Roger Quadros
2013-04-19 9:57 ` [PATCH v3 2/4] ARM: dts: omap3-beagle: Make USB host pin naming consistent Roger Quadros
2013-04-19 9:57 ` [PATCH v3 4/4] ARM: dts: omap3-beagle-xm: Add USB host supprot for Rev. Ax/Bx Roger Quadros
2013-04-19 15:43 ` [PATCH v3 0/4] ARM: dts: Add USB host support for Panda and Beagle-xm Tony Lindgren
2013-04-22 7:10 ` Roger Quadros
2013-04-25 15:34 ` Tony Lindgren [this message]
[not found] ` <1366365457-28972-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2013-04-19 9:57 ` [PATCH v3 1/4] ARM: dts: omap4-panda: Add USB Host support Roger Quadros
2013-04-19 9:57 ` [PATCH v3 3/4] ARM: dts: omap3-beagle-xm: " Roger Quadros
2013-04-29 12:32 ` [PATCH v3 0/4] ARM: dts: Add USB host support for Panda and Beagle-xm Roger Quadros
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=20130425153417.GI5184@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--cc=ravibabu@ti.com \
--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).