From: Felipe Balbi <balbi@ti.com>
To: Keshava Munegowda <keshava_mgowda@ti.com>
Cc: linux-omap@vger.kernel.org, linux-usb@vger.kernel.org,
balbi@ti.com, parthab@india.ti.com, govindraj.raja@ti.com
Subject: Re: [PATCH] ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue
Date: Fri, 24 Feb 2012 12:16:33 +0200 [thread overview]
Message-ID: <20120224101632.GL17178@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <1330077975-31694-1-git-send-email-keshava_mgowda@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
Hi,
On Fri, Feb 24, 2012 at 03:36:15PM +0530, Keshava Munegowda wrote:
> From: Keshava Munegowda <Keshava_mgowda@ti.com>
>
> It is observed that the echi ports of 3430 sdp board
> are not working due to the random timing of programming
> the associated GPIOs of the ULPI PHYs of the EHCI for reset.
> If the PHYs are reset at during usbhs core driver, host ports will
> not work because EHCI driver is loaded after the resetting PHYs.
> The PHYs should be in reset state while initializing the EHCI
> controller.
> The code which does the GPIO pins associated with the PHYs
> are programmed to reset is moved from the USB host core driver
> to EHCI driver.
>
> Signed-off-by: Keshava Munegowda <keshava_mgowda@ti.com>
> Reviewed-by: Partha Basak <parthab@india.ti.com>
won't this cause issues with EHCI/OHCI interactions ? I mean, what if
you connect a FS/LS device and port is handed over to OHCI, does OHCI
have any needs to reset the PHY or something similar ?
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-24 10:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 10:06 [PATCH] ARM: OMAP3: USB: Fix the EHCI ULPI PHY reset issue Keshava Munegowda
2012-02-24 10:16 ` Felipe Balbi [this message]
2012-02-24 11:44 ` Munegowda, Keshava
2012-03-02 14:06 ` Munegowda, Keshava
2012-03-08 15:00 ` Munegowda, Keshava
2012-03-16 16:20 ` Samuel Ortiz
2012-03-19 6:18 ` Munegowda, Keshava
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=20120224101632.GL17178@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=govindraj.raja@ti.com \
--cc=keshava_mgowda@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=parthab@india.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).