public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com>
To: ext Kevin Hilman <khilman@deeprootsystems.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 0/1] OMAP3 PM Add C0 state
Date: Tue, 24 Feb 2009 12:27:09 +0200	[thread overview]
Message-ID: <20090224102709.GA4569@codecarver.research.nokia.com> (raw)
In-Reply-To: <87ljrx9fl3.fsf@deeprootsystems.com>

On Mon, Feb 23, 2009 at 07:24:24PM +0100, ext Kevin Hilman wrote:
> "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com> writes:
> 
> > This patch introduces a new C state C0 which keeps both core and mpu
> > powerdomains in ON state. This gives us low latency at a cost of higher
> > power consumption.
> >
> 
> I don't like the name 'C0' for an idle-state.  In ACPI terms, C0 is an
> active state, not an idle state.  I know this is not an ACPI system,
> but since we're using ACPI names, we should be consistent.
> 
> Is there a real benefit to having an additional state here?  Shouldn't
> we just make these changes or C1?
> 

C1 has a too high wakeup latency (10s of us) for some cases, but C0 (which has
a 3us wakeup latency) keeps core on which implies little powersavings. So
I think we need both.

Cheers,

Peter.

-- 
goa is a state of mind

      reply	other threads:[~2009-02-24 10:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 16:21 [PATCH 0/1] OMAP3 PM Add C0 state Peter 'p2' De Schrijver
2009-02-18 16:21 ` [PATCH 1/1] " Peter 'p2' De Schrijver
2009-02-23 18:24 ` [PATCH 0/1] " Kevin Hilman
2009-02-24 10:27   ` Peter 'p2' De Schrijver [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=20090224102709.GA4569@codecarver.research.nokia.com \
    --to=peter.de-schrijver@nokia.com \
    --cc=khilman@deeprootsystems.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