From: Kevin Hilman <khilman@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: v3.5-rc4 doesn't wake from dynamic idle on 3530ES3 Beagle
Date: Wed, 27 Jun 2012 13:26:34 -0500 [thread overview]
Message-ID: <87k3ysr4px.fsf@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206271101220.27496@utopia.booyaka.com> (Paul Walmsley's message of "Wed, 27 Jun 2012 11:03:35 -0600 (MDT)")
Paul Walmsley <paul@pwsan.com> writes:
> Looks like something broke between v3.5-rc3 and v3.5-rc4 with dynamic
> idle on 3530ES3 Beagle. 37xx EVM doesn't seem to be affected.
>
> Taking a closer look now.
I don't currently have access to a 3530 Beagle so I couldn't test there,
but just confirmed that vanilla v3.5-rc4 wakes up from dynamic idle (via
serial console) on 3430/n900, 3730/OveroSTORM and 3730/Beagle-xM.
Sounds like it may be something specific to Beagle board changes?
Kevin
next prev parent reply other threads:[~2012-06-27 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-27 17:03 v3.5-rc4 doesn't wake from dynamic idle on 3530ES3 Beagle Paul Walmsley
2012-06-27 18:26 ` Kevin Hilman [this message]
2012-06-27 19:27 ` Paul Walmsley
2012-06-28 6:15 ` Shilimkar, Santosh
2012-07-02 10:22 ` Shubhrajyoti
2012-07-03 11:40 ` Datta, Shubhrajyoti
2012-07-04 3:06 ` Paul Walmsley
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=87k3ysr4px.fsf@ti.com \
--to=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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.