public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: eduardo.valentin@nokia.com
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Broken cpuidle on PM branch?
Date: Wed, 14 Oct 2009 06:06:41 -0700	[thread overview]
Message-ID: <87aazugm5a.fsf@deeprootsystems.com> (raw)
In-Reply-To: <20091014064822.GA1000@esdhcp037198.research.nokia.com> (Eduardo Valentin's message of "Wed\, 14 Oct 2009 09\:48\:22 +0300")

Eduardo Valentin <eduardo.valentin@nokia.com> writes:

> On Tue, Oct 13, 2009 at 06:25:17PM +0200, ext Kevin Hilman wrote:
>> Eduardo Valentin <eduardo.valentin@nokia.com> writes:
>> 
>> > Hello Amit,
>> >
>> > On Mon, Oct 12, 2009 at 09:23:47PM +0200, ext Amit Kucheria wrote:
>> >> Hi,
>> >> 
>> >> I am testing twl4030 script optimisations on the current PM branch. But I am
>> >> seeing the board (RX51) freeze when CPU_IDLE is enabled in the config.
>> >> 
>> >> Is it known to work on other boards?
>> >
>> > I'm actually seeing this same behavior. But the board actually does not
>> > freeze. If you keep a key pressed of send a sysrq through serial line
>> > then you eventually get it back.
>> >
>> > It seams to be something related to serial driver and wakeup ?
>> >
>> 
>> Do you see this problem after doing
>> 
>>   # echo 1 > /debug/pm_debug/sleep_while_idle
>> 
>
> No I don't. The problem is gone it seams.
>
> similar effect happens if we
>
> # echo 0 > /sys/devices/platform/serial8250.2/sleep_timeout
>
> Of course, this would prevent device go to sleep I guess.
>

Yes, there is a problem with UART3 (in PER) going idle independently
of CORE/MPU that I have not yet found.

Kevin


  reply	other threads:[~2009-10-14 13:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12 19:23 Broken cpuidle on PM branch? Amit Kucheria
2009-10-13 13:31 ` Eduardo Valentin
2009-10-13 16:25   ` Kevin Hilman
2009-10-14  6:48     ` Eduardo Valentin
2009-10-14 13:06       ` Kevin Hilman [this message]
2009-10-14 13:11         ` Eduardo Valentin
2009-10-13 14:05 ` Kevin Hilman

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=87aazugm5a.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=eduardo.valentin@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    /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