From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: Niilo Minkkinen <ext-niilo.1.minkkinen@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"tony@atomide.com" <tony@atomide.com>
Subject: Re: [PATCH] usb: disable OTG AUTOIDLE only with omap3430
Date: Tue, 19 May 2009 09:57:14 -0700 [thread overview]
Message-ID: <874ovh6nf9.fsf@deeprootsystems.com> (raw)
In-Reply-To: <13B9B4C6EF24D648824FF11BE8967162038BED5CF1@dlee02.ent.ti.com> (Richard Woodruff's message of "Mon\, 18 May 2009 14\:23\:11 -0500")
"Woodruff, Richard" <r-woodruff2@ti.com> writes:
>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
>> owner@vger.kernel.org] On Behalf Of Niilo Minkkinen
>> Sent: Monday, May 18, 2009 9:54 AM
>
>> Omap3 MUSB AUTOIDLE functionality configured through OTG_SYSCONFIG
>> register prevents the device from going into retention.
>> This is a workaround (by Richard Woodruff/TI), as his comment :
>> > A new MUSB bug which is a match to data below was identified very
>> > recently (on hardware and in simulation).
>> > This bug is in 3430 and not 3630.
>> > As a priority test (and as new default) you should have engineers
>> > disable autoidle for MUSB block.
>> > This is the workaround which will show up in next errata.
>>
>> Signed-off-by: Niilo Minkkinen <ext-niilo.1.minkkinen@nokia.com>
>
> Signed-off-by: Richard Woodruff <r-woodruff2@ti.com>
>
> Yes this is needed for 34xx. Side note is this cost around 1mW of power during active mode of MUSB. When device is not active cost is not significant. System impact depends on duty cycle of MUSB in usecase.
>
While this makes its way upstream, I'll pull into PM branch.
Kevin
next prev parent reply other threads:[~2009-05-19 16:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-18 14:54 [PATCH] usb: disable OTG AUTOIDLE only with omap3430 Niilo Minkkinen
[not found] ` <1242658456-5723-1-git-send-email-ext-niilo.1.minkkinen-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2009-05-18 19:23 ` Woodruff, Richard
2009-05-19 16:57 ` Kevin Hilman [this message]
[not found] ` <13B9B4C6EF24D648824FF11BE8967162038BED5CF1-EovWT4A8QTWIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2009-06-19 10:35 ` David Brownell
[not found] ` <200906190335.50621.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2009-06-19 16:45 ` Niilo Minkkinen
2009-08-26 11:47 ` Gupta, Ajay Kumar
[not found] ` <19F8576C6E063C45BE387C64729E73940436A4A15B-/tLxBxkBPtCIQmiDNMet8wC/G2K4zDHf@public.gmane.org>
2009-08-26 13:53 ` Niilo Minkkinen
[not found] ` <fb705f540908260653l990f173n8b953ebc893efb9e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-26 14:52 ` Pandita, Vikram
2009-08-27 1:27 ` Gupta, Ajay Kumar
2009-08-28 5:08 ` 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=874ovh6nf9.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=ext-niilo.1.minkkinen@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@ti.com \
--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