From: Tony Lindgren <tony@atomide.com>
To: "Gupta, Ajay Kumar" <ajay.gupta@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"felipe.balbi@nokia.com" <felipe.balbi@nokia.com>,
"david-b@pacbell.net" <david-b@pacbell.net>
Subject: Re: [PATCH 5/9] ehci: increase timeout to fix ehci failure
Date: Tue, 22 Sep 2009 10:10:27 -0700 [thread overview]
Message-ID: <20090922171027.GD14890@atomide.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E73940436C43D6F@dbde02.ent.ti.com>
* Gupta, Ajay Kumar <ajay.gupta@ti.com> [090922 06:10]:
> Tony,
> > * Ajay Kumar Gupta <ajay.gupta@ti.com> [090806 05:13]:
> > > Sometime during TLL reset and waiting loop for TLL reset timeouts and
> > thus
> > > ehci init fails. Fixing this by increasing timeout value.
> >
> > Applying patches 6 - 9 to ehci branch also.
>
> One patch is missing which causes compilation error.
> [0002-omap3-Add-CHIP_GE_OMAP3430ES3-for-HSUSB.patch]
OK, after looking at the "ehci: Support for ES3.x" patch more,
how about just testing the revision with:
if (omap_rev() == OMAP3430_REV_ES3_1) {
/* Set something */
}
That means the 0002-omap3-Add-CHIP_GE_OMAP3430ES3-for-HSUSB.patch
is not needed.
So I'm dropping the "ehci: Support for ES3.x" patch for now.
> Apart from this I have two more EHCI fixes and one patch to fix compilation warning on OMAP3EVM.
>
> I am submitting all four patches , Please review them.
Pushing the others to the ehci branch.
Tony
next prev parent reply other threads:[~2009-09-22 17:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 12:07 [PATCH 1/9] ehci: fix ehci pin mux init Ajay Kumar Gupta
2009-08-06 12:07 ` [PATCH 2/9] ehci: adding mux pin for EHCI phy reset line Ajay Kumar Gupta
2009-08-06 12:07 ` [PATCH 3/9] ehci: correct EHCI init parameters on OMAP3EVM Ajay Kumar Gupta
2009-08-06 12:07 ` [PATCH 4/9] ehci: fix phy_reset init in ehci probe Ajay Kumar Gupta
2009-08-06 12:07 ` [PATCH 5/9] ehci: increase timeout to fix ehci failure Ajay Kumar Gupta
2009-08-06 12:07 ` [PATCH 6/9] ehci: portwise configurations Ajay Kumar Gupta
2009-08-06 12:07 ` [PATCH 7/9] omap3: Add CHIP_GE_OMAP3430ES3 for HSUSB Ajay Kumar Gupta
2009-08-06 12:07 ` [PATCH 8/9] ehci: Support for ES3.x Ajay Kumar Gupta
2009-08-06 12:07 ` [PATCH 9/9] ehci: update driver with generic change Ajay Kumar Gupta
2009-08-06 13:07 ` [PATCH 7/9] omap3: Add CHIP_GE_OMAP3430ES3 for HSUSB Felipe Balbi
2009-08-06 13:13 ` Tony Lindgren
2009-09-22 1:10 ` [PATCH 5/9] ehci: increase timeout to fix ehci failure Tony Lindgren
2009-09-22 13:10 ` Gupta, Ajay Kumar
2009-09-22 17:10 ` Tony Lindgren [this message]
2009-09-22 1:02 ` [PATCH 4/9] ehci: fix phy_reset init in ehci probe Tony Lindgren
2009-08-06 12:43 ` [PATCH 3/9] ehci: correct EHCI init parameters on OMAP3EVM Tony Lindgren
2009-08-07 9:06 ` Gupta, Ajay Kumar
2009-09-22 0:59 ` Tony Lindgren
2009-09-22 0:55 ` [PATCH 2/9] ehci: adding mux pin for EHCI phy reset line Tony Lindgren
2009-08-06 12:40 ` [PATCH 1/9] ehci: fix ehci pin mux init Tony Lindgren
2009-08-06 13:45 ` Gupta, Ajay Kumar
2009-08-06 14:02 ` Gadiyar, Anand
2009-08-06 14:31 ` Gupta, Ajay Kumar
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=20090922171027.GD14890@atomide.com \
--to=tony@atomide.com \
--cc=ajay.gupta@ti.com \
--cc=david-b@pacbell.net \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.