public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Adam Belay <abelay@novell.com>
Cc: linux-pm@lists.osdl.org
Subject: Re: [RFC] Linux Power Management
Date: Tue, 3 May 2005 23:40:09 +0200	[thread overview]
Message-ID: <20050503214009.GE10404@elf.ucw.cz> (raw)
In-Reply-To: <1115094736.28902.167.camel@localhost.localdomain>

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

Hi!

> Device Drivers
> ==============
> 
> Linux device drivers must often save and restore state during power
> transitions.  The following API is proposed:
> 
> ->prepare_state(struct device * dev, pm_state_t state,
>                 unsigned int reason);
> ->complete_state(struct device * dev, pm_state_t state,
>                 unsigned int reason);
> 
> The following would be an example of a typical transition:
> 
> 1.) the policy manager decides to put a PCI ethernet card into D3 from
> D0.
> 2.) ->prepare_state is called, the ethernet driver saves its state
> information and disables the hardware
> 3.) the power driver's ->set_state function is called, and power is
> actually removed.
> 4.) ->complete_state is called to cleanup and make any final
> adjustments.
> 
> * In the case of D3->D0 ->complete_state would restore state.
> 
> Possible "reasons" might include DYNAMIC_PM, HALT, REBOOT, SUSPEND,
> RESUME, etc.
> 
> This API is different from the current ->suspend and ->resume because it
> applies to situations outside of system suspend (e.g. runtime power
> management) and has an emphasis on specific device power states. 

No. It took 2+ years to add at at least system power states. You want
to build on that, not scratch it and start over.

								Pavel
-- 
Boycott Kodak -- for their patent abuse against Java.

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



  parent reply	other threads:[~2005-05-03 21:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03  4:32 [RFC] Linux Power Management Adam Belay
2005-05-03  6:06 ` Nigel Cunningham
2005-05-03 15:52 ` Alan Stern
2005-05-05  4:39   ` Adam Belay
2005-05-08 18:35     ` David Brownell
2005-05-09  9:49       ` Pavel Machek
2005-05-09 16:41         ` David Brownell
2005-05-09 19:30           ` Pavel Machek
2005-05-03 21:40 ` Pavel Machek [this message]
2005-05-05  4:12   ` Adam Belay
2005-05-05  9:38     ` Pavel Machek
2005-05-08 18:39       ` David Brownell
2005-05-09  8:35         ` Pavel Machek
2005-05-08 18:31 ` David Brownell
2005-05-09  3:26   ` Adam Belay
2005-05-09 16:02     ` David Brownell

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=20050503214009.GE10404@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=abelay@novell.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