linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@linaro.org>
To: Roger Quadros <rogerq@ti.com>
Cc: Felipe Balbi <balbi@ti.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	Mike Turquette <mturquette@linaro.com>
Subject: Re: OMAP EHCI having clock problems?
Date: Mon, 18 Feb 2013 06:47:44 -0800	[thread overview]
Message-ID: <87a9r165m7.fsf@linaro.org> (raw)
In-Reply-To: <5121F945.1020907@ti.com> (Roger Quadros's message of "Mon, 18 Feb 2013 11:49:57 +0200")

Roger Quadros <rogerq@ti.com> writes:

> On 02/15/2013 05:54 PM, Kevin Hilman wrote:
>> Roger Quadros <rogerq@ti.com> writes:
>> 
>>> Hi Kevin,
>>>
>>> On 02/15/2013 12:50 AM, Kevin Hilman wrote:
>>>> Felipe, Roger,
>>>>
>>>> Using Tony's current master branch, and enabling EHCI support, I see 
>>>> the clock framework spitting loudly about the EHCI driver (full boot log
>>>> below.)   The same thing happens on v3.8-rc7.
>>>>
>>>> Any idea what's going on?  Am I missing a set of fixes that's already
>>>> been posted?
>>>
>>> Thanks for pointing out. This series should fix the issues
>>> https://lkml.org/lkml/2013/1/23/155
>>>
>>> They should be on their way to linux-next.
>> 
>> Great.  But what about v3.8?  I see the same problems in v3.8-rc7.
>> 
>
> Kevin, the fix is below for older kernels.

Tested-by: Kevin Hilman <khilman@linaro.org>

Thanks, tested on v3.8-rc and works great.  Are you planning on
submitting this for v3.8 via stable? 

Thanks,

Kevin

  reply	other threads:[~2013-02-18 14:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 22:50 OMAP EHCI having clock problems? Kevin Hilman
2013-02-15  5:12 ` Mike Turquette
2013-02-15  7:54 ` Roger Quadros
2013-02-15 15:54   ` Kevin Hilman
2013-02-15 16:04     ` Felipe Balbi
2013-02-18  9:49     ` Roger Quadros
2013-02-18 14:47       ` Kevin Hilman [this message]
2013-02-18 14:51         ` 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=87a9r165m7.fsf@linaro.org \
    --to=khilman@linaro.org \
    --cc=balbi@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mturquette@linaro.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).