From: Felipe Balbi <felipe.balbi@nokia.com>
To: ext Ajay Kumar Gupta <ajay.gupta@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>,
"Balbi Felipe (Nokia-D/Helsinki)" <felipe.balbi@nokia.com>
Subject: Re: [PATCH] ehci: fix ehci pin mux init
Date: Fri, 3 Jul 2009 13:47:15 +0300 [thread overview]
Message-ID: <20090703104715.GA4323@nokia.com> (raw)
In-Reply-To: <1246617561-8644-1-git-send-email-ajay.gupta@ti.com>
On Fri, Jul 03, 2009 at 12:39:21PM +0200, ext Ajay Kumar Gupta wrote:
> EHCI pin mux init fucntion is still using old #ifdef
> which are not defined anymore.This causes pin mux init to
> always set TLL settings and thus EHCI PHY mode doesn't work.
>
> Fixing this issue by using phy_mode parameter to initialize
> mux settings.
>
> Signed-off-by: Ajay Kumar Gupta <ajay.gupta@ti.com>
Acked-by: Felipe Balbi <felipe.balbi@nokia.com>
--
balbi
next prev parent reply other threads:[~2009-07-03 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 10:39 [PATCH] ehci: fix ehci pin mux init Ajay Kumar Gupta
2009-07-03 10:47 ` Felipe Balbi [this message]
2009-09-22 0:47 ` Tony Lindgren
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=20090703104715.GA4323@nokia.com \
--to=felipe.balbi@nokia.com \
--cc=ajay.gupta@ti.com \
--cc=linux-omap@vger.kernel.org \
--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