public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Tero Kristo <tero.kristo@nokia.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCHv6] OMAP3: Serial: Improved sleep logic
Date: Wed, 10 Mar 2010 10:20:54 -0800	[thread overview]
Message-ID: <87aaugf37d.fsf@deeprootsystems.com> (raw)
In-Reply-To: <87ljebdb3c.fsf@deeprootsystems.com> (Kevin Hilman's message of "Mon\, 01 Mar 2010 12\:46\:15 -0800")

Kevin Hilman <khilman@deeprootsystems.com> writes:

> Tero Kristo <tero.kristo@nokia.com> writes:
>
>> From: Tero Kristo <tero.kristo@nokia.com>
>>
>> This patch contains following improvements:
>> - Only RX interrupt will now kick the sleep prevent timer
>> - TX fifo status is checked before disabling clocks, this will prevent
>>   on-going transmission to be cut
>> - Smartidle is now enabled/disabled only while switching clocks, as having
>>   smartidle enabled while RX/TX prevents any wakeups from being received
>>   from UART module
>> - Added workqueue for wakeup checks, as jiffy timer access within the
>>   idle loop results into skewed timers as jiffy timers are stopped
>> - Added garbage_timer for ignoring the first character received during
>>   the first tick after clock enable, this prevents garbage characters to be
>>   received in low sleep states
>> - omap_uart_enable_irqs() changed to use enable_irq / disable_irq instead
>>   of request / free. Using request/free changes the behavior after first
>>   suspend due to reversed interrupt handler ordering
>>
>> Signed-off-by: Tero Kristo <tero.kristo@nokia.com>
>
> Thanks Tero.  This version looks good.
>
> Adding to pm-fixes queue for 2.6.34-rcX after minor change below...
>

There's still something slightly strange going on here...

I noticed via powertop that the garbage timer is now one of the top
reasons for wakeup in an idle system.  Seems like the garbage timer
is firing when it shouldn't be, and triggering unnecessary wakeups

Based on powertop stats, the garbage timer is firing about 3x more
often than the GPtimer that should be waking the system.

I haven't dug any deeper, but this needs to be fixed before merging
upstream.

Kevin

  reply	other threads:[~2010-03-10 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 17:25 [PATCHv6] OMAP3: Serial: Improved sleep logic Tero Kristo
2010-03-01 20:46 ` Kevin Hilman
2010-03-10 18:20   ` Kevin Hilman [this message]
2010-03-11 16:20     ` Tero.Kristo
2010-03-11 16:29       ` Kevin Hilman
2010-03-11 17:07         ` Tero.Kristo

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=87aaugf37d.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tero.kristo@nokia.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