From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>, linux-omap <linux-omap@vger.kernel.org>
Subject: Re: OMAP4460/PandaES: hang during resume
Date: Wed, 03 Oct 2012 07:22:33 -0700 [thread overview]
Message-ID: <87a9w33aae.fsf@deeprootsystems.com> (raw)
In-Reply-To: <CAMQu2gy7jdsiEenoE_GkpHRj2CGoySMS7LCo-PrfN-76hn02Vg@mail.gmail.com> (Santosh Shilimkar's message of "Wed, 3 Oct 2012 13:33:04 +0530")
"Shilimkar, Santosh" <santosh.shilimkar@ti.com> writes:
> On Wed, Oct 3, 2012 at 5:05 AM, Kevin Hilman
> <khilman@deeprootsystems.com> wrote:
>> Hi Santosh, Tero,
>>
>> I just added my 4460/PandaES to my board farm for automated PM testing
>> and see that basic suspend/resume tests don't work in mainline. It
>> fails on v3.6 and linux-next,arm-soc/for-next.
>>
>> Adding 'no_console_suspend' to the cmdline shows me that wakeup event is
>> happening so the hang is somewhere during resume. I haven't dug any
>> deeper than that.
>>
>> This works fine on 4430/Panda. Do you know of anything else we're
>> missing in mainline for a basic suspend/resume test on 4430?
>>
> OMAP4460 has one ROM code BUG which impacts MPUSS OSWR.
> I suspect you are missing that Errata WA.
> You need a patch [1] which is in Tero's CORE RET series.
Ah, yes. The one where I asked you to q(re)write the change log a hundred
times. How could I forget. ;)
Thanks for the reminder.
Kevin
prev parent reply other threads:[~2012-10-03 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87txuc4fd1.fsf@deeprootsystems.com>
2012-10-03 8:03 ` OMAP4460/PandaES: hang during resume Shilimkar, Santosh
2012-10-03 14:22 ` Kevin Hilman [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=87a9w33aae.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.com \
--cc=t-kristo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.