From: Adam Belay <ambx1@neo.rr.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-pm@lists.osdl.org
Subject: Re: [RFC] A New Power Management API
Date: Sun, 17 Apr 2005 19:01:48 -0400 [thread overview]
Message-ID: <20050417230147.GC7793@neo.rr.com> (raw)
In-Reply-To: <200504171529.17711.david-b@pacbell.net>
[-- Attachment #1: Type: text/plain, Size: 897 bytes --]
On Sun, Apr 17, 2005 at 03:29:17PM -0700, David Brownell wrote:
> On Sunday 17 April 2005 1:48 pm, Adam Belay wrote:
> >
> > So I think each clock could be a power resource. It looks like the
> > current code isn't doing much more than turning them on and off.
>
> They should clk_use()/clk_unuse(), and automatically handle the
> activation/deactivation of parent clocks. Some clocks are shared
> between multiple devices ... so "on/off" doesn't suffice, those
> devices' drivers rely on the clock framework to coordinate. (Or
> were you thinking that on/off would match use/unuse? There's no
> point to separate enable/disable calls IMO.)
Yes, I was thinking power resources could replace use/unuse. So each device
could associate a list of required resources by state. Then, when there
are not any devices in a state that requires a given resource, the resource
could be turned off.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2005-04-17 23:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 2:46 [RFC] A New Power Management API Adam Belay
2005-04-15 8:21 ` Benjamin Herrenschmidt
2005-04-15 13:16 ` Daniel Petrini
2005-04-15 18:20 ` Adam Belay
2005-04-16 17:13 ` David Brownell
2005-04-17 20:26 ` Adam Belay
2005-04-15 15:50 ` Jordan Crouse
2005-04-15 18:54 ` Adam Belay
2005-04-16 2:53 ` Todd Poynor
2005-04-16 19:26 ` David Brownell
2005-04-19 3:09 ` Todd Poynor
2005-05-08 19:05 ` David Brownell
2005-04-16 18:24 ` David Brownell
2005-04-17 20:48 ` Adam Belay
2005-04-17 22:29 ` David Brownell
2005-04-17 23:01 ` Adam Belay [this message]
2005-04-16 17:27 ` David Brownell
2005-04-17 20:25 ` Adam Belay
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=20050417230147.GC7793@neo.rr.com \
--to=ambx1@neo.rr.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