public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Richard A. Griffiths" <richard.griffiths@windriver.com>
To: "Brown, Len" <len.brown@intel.com>
Cc: linux-pm@lists.osdl.org
Subject: RE: on-ness
Date: Mon, 17 Apr 2006 14:52:26 -0700	[thread overview]
Message-ID: <1145310746.2913.2.camel@localhost.localdomain> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB63588C3@hdsmsx411.amr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2004 bytes --]

see below.

On Mon, 2006-04-17 at 17:43 -0400, Brown, Len wrote:
> > Thinking about the discussion of the ON field. How about Limiter? Then
> 0
> > maps to no limit (max power, max freq, whatever) and any other number
> is
> > some limit of performance/power, similar to what was decided for Idle.
> 
> my scribbles on generic sysfs device directory file names say:
> 
> state:
> on	- running and available
> off	- requires a full device initialization to be usable
> 
> idle: # = "how idle"
> 0 - active, not idle at all eg C0, D0
> 1 - idle. eg C1, D1
> ...
> n - most power saving, highest latency idle state, eg. Cn, Dn
> 
> idle_max
> max # that can be in idle file above
> 
> speed: # = "how fast"
> 0 - minimum speed
> 1 - 
> ...
> n -- highest speed, highest power
> 
> speed_max
> max # that can be in speed file above
> 
> So describing the ACPI states using these:
> 
> state = on: online
> state = off: offline
> 
> idle = 0: C0
> idle = 1: C1
> idle = n: Cn
> 
> (for devices with D-states, replace Cx above with Dx -- since they are
> both describing a state where the device is present, but not executing
> and with increasing latency before resuming execution)
> 
> speed = 0: Pn
> speed = 1: Pn-1
> ...
> speed = n: P0
> 
> Not immediately obvious how to articulate Throttling states here,
> would probably need an additional file similar to "speed", since they
> are effectively multiplied.  Maybe simply:
> 
> throttle
> 0 - full speed
> n - min speed
> 
> Re: state
> unclear if on/off is sufficient, or if hotplug wold need any
> other states.
> 
> ---
> 
> sounds like you're suggesting the inverse of "speed" where
> 0 is max performance and max power.  I'd certainly be happy
> to have 0 mean P0 for processors -- but "on" and "speed"
> are certainly the opposite of what we want to call this.
> Maybe "powersave" to capture the concept of an executing
> but power saving operating point?
I like powersave. Then 0 indicates an ON state with no power
saving.  Good idea.

Richard


[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2006-04-17 21:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-17 21:43 on-ness Brown, Len
2006-04-17 21:52 ` Richard A. Griffiths [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=1145310746.2913.2.camel@localhost.localdomain \
    --to=richard.griffiths@windriver.com \
    --cc=len.brown@intel.com \
    --cc=linux-pm@lists.osdl.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