From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Anand Gadiyar <gadiyar@ti.com>,
linux-omap@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>,
Felipe Balbi <balbi@ti.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Benoit Cousson <b-cousson@ti.com>
Subject: Re: [PATCH] arm: omap4: pandaboard: turn on PHY reference clock at init
Date: Mon, 10 Jan 2011 11:12:01 -0800 [thread overview]
Message-ID: <20110110191201.GG4957@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1101101152040.5731@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [110110 10:51]:
> On Mon, 10 Jan 2011, Anand Gadiyar wrote:
>
> > The SMSC 3320 USB PHY on the OMAP4 Pandaboard needs a 19.2 MHz
> > reference clock. This clock is provided from the OMAP4's fref_clk3
> > pad.
> >
> > Recent changes to clock44xx_data.c made the clock framework aware
> > of the existence of these fref_clk[i] lines. If the option
> > CONFIG_OMAP_RESET_CLOCKS is enabled in the kernel, then the
> > clock framework will turn these clocks off during bootup.
> >
> > Explicitly request and keep this clock enabled at init for the
> > Pandaboard, so that the PHY receives this clock at all times.
> >
> > Reported-by: Ming Lei <tom.leiming@gmail.com>
> > Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
> > Cc: Benoit Cousson <b-cousson@ti.com>
> > Cc: Paul Walmsley <paul@pwsan.com>
> > Cc: Tony Lindgren <tony@atomide.com>
>
> Reviewed-by: Paul Walmsley <paul@pwsan.com>
Will queue as a fix.
Tony
prev parent reply other threads:[~2011-01-10 19:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 14:42 [PATCH] arm: omap4: pandaboard: turn on PHY reference clock at init Anand Gadiyar
2011-01-10 15:43 ` Ming Lei
2011-01-10 15:54 ` Felipe Balbi
2011-01-10 16:17 ` Anand Gadiyar
2011-01-10 18:52 ` Paul Walmsley
2011-01-10 19:12 ` Tony Lindgren [this message]
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=20110110191201.GG4957@atomide.com \
--to=tony@atomide.com \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=gadiyar@ti.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=sfr@canb.auug.org.au \
/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