public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: david-b@pacbell.net
Cc: linux-pm@lists.osdl.org
Subject: Re: Toward runtime power management in Linux
Date: Thu, 4 Aug 2005 01:06:49 -0700	[thread overview]
Message-ID: <20050804080649.GF22000@atomide.com> (raw)
In-Reply-To: <20050802024415.C3518DB57B@adsl-69-107-32-110.dsl.pltn13.pacbell.net>

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

* david-b@pacbell.net <david-b@pacbell.net> [050801 19:44]:
> > From: Amit Kucheria <amit.kucheria@nokia.com>
> > Date: Mon, 01 Aug 2005 14:44:46 +0300
> >
> > ...
> > If I tell a bus
> 
> (... or any other device with child nodes, like a USB hub or
> various system bridges ...)
> 
> 
> >	to power down, couldn't the PM framework take care of
> > recursively sending 'power down' message to all children, wait for
> > confirmation, and then power itself down?
> 
> Could, arguably should -- but doesn't, just now.  I don't
> think I'd try to manage all system devices' power through
> sysfs from usermode yet ... :)

There are some cases where the whole bus can be powered down, but
a device on the bus needs to be left on to provide wake-up events.

The wake-up event might take another path, such as GPIO, and the
bus can be powered down with some devices on.

An example that comes to mind is the smc91x Ethernet driver on
OMAP OSK board.

Regards,

Tony

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



  parent reply	other threads:[~2005-08-04  8:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31  2:36 Toward runtime power management in Linux Alan Stern
2005-08-01  2:10 ` Leo L. Schwab
2005-08-01 11:44   ` Amit Kucheria
2005-08-01 14:16     ` Alan Stern
     [not found]     ` <20050802024415.C3518DB57B@adsl-69-107-32-110.dsl.pltn13.pacbell.net>
2005-08-04  8:06       ` Tony Lindgren [this message]
2005-08-04 16:02         ` david-b
2005-08-14 19:53         ` Pavel Machek
2005-08-01 14:07   ` Alan Stern
2005-08-01 15:10     ` Jordan Crouse
2005-08-01 15:23       ` Alan Stern
2005-08-04 17:24     ` Igor Stoppa
     [not found] ` <Pine.LNX.4.50.0508011712220.2764-100000@monsoon.he.net>
2005-08-02 17:45   ` Geoff Levand
2005-08-25  3:12 ` Benjamin Herrenschmidt
2005-08-25 15:27   ` Alan Stern
2005-08-25 21:42     ` Benjamin Herrenschmidt
2005-08-26  2:25       ` Alan Stern
     [not found] <Pine.LNX.4.50.0508012316380.2764-100000@monsoon.he.net>
2005-08-02 14:35 ` Alan Stern
  -- strict thread matches above, loose matches on Subject: below --
2005-08-25 13:59 Brown, Len

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=20050804080649.GF22000@atomide.com \
    --to=tony@atomide.com \
    --cc=david-b@pacbell.net \
    --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