All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa.com>
To: ppc-dev <linuxppc-dev@ozlabs.org>
Subject: e600 core power management
Date: Mon, 07 Jul 2008 12:48:09 +0100	[thread overview]
Message-ID: <48720279.6010904@genesi-usa.com> (raw)

Hi guys,

Quick question, am I right (and looking at idle_6xx.S, I think I am) in thinking that
during the idle process, by default, an e600 core such as the 7448 or MPC8610 will
automatically transition to a NAP state, thus being as low power as possible?

Has anyone done any benchmarking of the power consumption of the processor when
this transition is disabled (remove CPU_FTR_MAYBE_CAN_NAP) or have a rough idea
what the benefits might be?

Is there a performance reason for removing the feature or disabling naps altogether?
The powersave-nap sysctl controls whether DOZE or NAP is entered on processors that
support a seperate HID0[DOZE], however is it possible to extend it such that nap
is never entered?

-- 
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations

             reply	other threads:[~2008-07-07 11:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07 11:48 Matt Sealey [this message]
2008-07-07 18:04 ` e600 core power management Matt Sealey

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=48720279.6010904@genesi-usa.com \
    --to=matt@genesi-usa.com \
    --cc=linuxppc-dev@ozlabs.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 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.