From: Kalle Jokiniemi <kalle.jokiniemi@digia.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
"tony@atomide.com" <tony@atomide.com>,
"paul@pwsan.com" <paul@pwsan.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Menon, Nishanth" <nm@ti.com>,
Kalle Jokiniemi <ext-kalle.jokiniemi@nokia.com>
Subject: RE: [PATCH] PM: Disable usb host HW save and restore
Date: Fri, 15 May 2009 09:44:34 +0300 [thread overview]
Message-ID: <1242369874.6466.213.camel@ubuntu> (raw)
In-Reply-To: <13B9B4C6EF24D648824FF11BE8967162038BE09C66@dlee02.ent.ti.com>
On Thu, 2009-05-14 at 20:40 +0300, Woodruff, Richard wrote:
> > From: Kevin Hilman [mailto:khilman@deeprootsystems.com]
> > Sent: Thursday, May 14, 2009 12:10 PM
> > To: Kalle Jokiniemi
>
> > Kalle Jokiniemi <kalle.jokiniemi@digia.com> writes:
> >
> > > The hardware SAVEANDRESTORE mechanism seems to leave
> > > USB HOST power domain permanently into active state
> > > after one transition from off to active state.
> > > Disabling for now.
>
> Some are is needed around USB host domain handling. There are a
> couple errata impacting different chip revs.
>
> Today in the older TI reference code this condition of a stuck on
> power domain does not happen. However, we are using a software
> supervised method to disable the power domain. May be this code has a
> bug or the hardware does around auto use for this domain.
Yes, usb-host autoidle was enabled when I was digging this issue.
>
> You will want TLL or host SAR activated to minimally work around a
> possible false cold reset issue. There is a window coming back from
> OFF where a reset will be thrown. Enabling SAR conclusively moves the
> internal window so there is no danger. The error is fairly easily
> seen so if you start taking resets know this is likely the root cause.
>
> What Rev of CPU is the issue occurring on?
I think the usb-host problem was on ES3.1 at least.
>
> The USBTLL SAR in 3.0 and before silicon will case a deadlock on 2nd
> sleep attempt. On 3.1 and after its fixed.
So ES3.0 devices are exposed to the cold reset issue (since USBTLL SAR
is only enabled in ES3.1). Would you suspect that we can enable USB host
SAR, if the AUTOIDLE is turned off? Then we would not need this patch.
- Kalle
>
> Regards,
> Richard W.
next prev parent reply other threads:[~2009-05-15 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 10:58 [PATCH] PM: Disable usb host HW save and restore Kalle Jokiniemi
2009-05-14 17:10 ` Kevin Hilman
2009-05-14 17:40 ` Woodruff, Richard
2009-05-15 6:44 ` Kalle Jokiniemi [this message]
2009-05-15 11:47 ` Woodruff, Richard
2009-05-15 13:52 ` Kalle Jokiniemi
2009-06-05 13:06 ` Nayak, Rajendra
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=1242369874.6466.213.camel@ubuntu \
--to=kalle.jokiniemi@digia.com \
--cc=ext-kalle.jokiniemi@nokia.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=paul@pwsan.com \
--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