From: Pavel Machek <pavel@ucw.cz>
To: Mark Gross <mgross@linux.intel.com>
Cc: linux-pm@lists.osdl.org
Subject: Re: So, what's the status on the recent patches here?
Date: Thu, 31 Aug 2006 00:27:22 +0200 [thread overview]
Message-ID: <20060830222714.GD3923@elf.ucw.cz> (raw)
In-Reply-To: <20060830221354.GA12186@linux.intel.com>
On Wed 2006-08-30 15:13:54, Mark Gross wrote:
> On Mon, Aug 28, 2006 at 07:39:57PM +0200, Pavel Machek wrote:
> > On Mon 2006-08-28 09:40:38, Mark Gross wrote:
> > > On Sat, Aug 26, 2006 at 03:46:53PM +0200, Pavel Machek wrote:
> > > > On Sat 2006-08-26 17:30:40, Vitaly Wool wrote:
> > > > > On 8/26/06, Pavel Machek <pavel@suse.cz> wrote:
> > > > Because 8388608 policies is clearly not reasonable, powerop can not
> > > > help here, and something better should be developed... like power
> > > > domains someone proposed here.
> > > >
> > > > (Or to say it in another words, powerop forces one big power domain,
> > > > which is bad model for notebook-style machine).
> > >
> > > I doubt notebook-style machines will ever us power op in any
> > > significant way. HPC and embedded will be the first users.
> >
> > I agree here... power op look useless for notebooks. But I doubt power
> > op authors would agree...
>
> Concluding that it will be useless for notebooks may be premature.
>
> I see powerop as the bottom of an future PM stack. As the upper layers
> take shape who knows what platforms will use it?
Well, PCs are generaly designed in a way where individual devices are
separate, and that means that we do not have linked-parameters-problem
powerop tries to solve. But okay, perhaps someone created such
notebook in future...
> > > Power domains will likely build on top power op.
> > >
> > > Power domains adds complexities themselves. Dealing with
> > > dependencies and constraints between domains will be a challenge.
> >
> > Once we have power domains in/solved... do we still need power op? I
> > thought power op could be useful for solving constrains _inside_ one
> > domain, but...
>
> Power domains and the components within them will likely be accessed as
> operating points. I think we need to build the power domain
> abstractions on top of operating points. This is why I want to see
> support for multiple power_op_driver instances or a story for how
> operating points are added to a running system or even platform to
> enable and deal with domains.
Yes, multiple power_op_drivers -- one per power domain -- makes some
sense.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-08-30 22:27 UTC|newest]
Thread overview: 136+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 20:07 So, what's the status on the recent patches here? Greg KH
2006-08-14 22:24 ` Matthew Locke
2006-08-14 22:46 ` Dave Jones
2006-08-14 23:24 ` Matthew Locke
2006-08-14 23:48 ` Dave Jones
2006-08-15 1:00 ` Greg KH
2006-08-15 3:03 ` Dave Jones
2006-08-15 10:35 ` Amit Kucheria
2006-08-15 19:04 ` Dave Jones
2006-08-16 12:58 ` Igor Stoppa
2006-08-17 21:39 ` Pavel Machek
2006-08-18 10:02 ` Igor Stoppa
2006-08-18 15:29 ` Alexey Starikovskiy
2006-08-18 17:54 ` Igor Stoppa
2006-08-18 21:05 ` Alexey Starikovskiy
2006-08-20 13:19 ` Igor Stoppa
2006-08-17 5:20 ` Matthew Locke
2006-08-17 7:20 ` Paul Mundt
2006-08-17 9:18 ` Amit Kucheria
2006-08-17 21:40 ` Pavel Machek
2006-08-18 5:42 ` Vitaly Wool
2006-08-23 12:28 ` Pavel Machek
2006-08-23 15:26 ` Igor Stoppa
2006-08-24 12:58 ` Vitaly Wool
2006-08-25 19:55 ` Pavel Machek
2006-08-25 23:26 ` Vitaly Wool
2006-08-26 10:18 ` Pavel Machek
2006-08-26 13:30 ` Vitaly Wool
2006-08-26 13:46 ` Pavel Machek
2006-08-28 16:40 ` Mark Gross
2006-08-28 17:39 ` Pavel Machek
2006-08-29 7:51 ` Matthew Locke
2006-08-30 22:13 ` Mark Gross
2006-08-30 22:27 ` Pavel Machek [this message]
2006-08-18 11:48 ` Amit Kucheria
2006-08-24 7:59 ` Pavel Machek
2006-08-30 11:00 ` Amit Kucheria
2006-08-30 22:36 ` Pavel Machek
2006-08-31 13:44 ` Amit Kucheria
2006-09-02 11:17 ` Pavel Machek
2006-08-17 21:24 ` Pavel Machek
2006-08-19 6:10 ` David Singleton
2006-08-22 2:13 ` Greg KH
2006-08-22 5:20 ` David Singleton
2006-08-23 19:05 ` Mark Gross
2006-08-24 12:39 ` Pavel Machek
2006-08-19 6:19 ` David Singleton
[not found] ` <20060819184843.GB15644@redhat.com>
2006-08-20 3:20 ` David Singleton
2006-08-20 3:30 ` Dave Jones
2006-08-23 18:50 ` Mark Gross
2006-08-27 4:37 ` David Singleton
2006-08-27 15:41 ` Pavel Machek
2006-08-29 15:55 ` David Singleton
2006-08-29 16:34 ` Pavel Machek
2006-08-29 17:49 ` Preece Scott-PREECE
2006-08-30 6:20 ` Matthew Locke
2006-08-30 13:26 ` Preece Scott-PREECE
2006-08-30 22:50 ` Pavel Machek
2006-08-31 0:22 ` Preece Scott-PREECE
2006-08-31 12:04 ` Pavel Machek
2006-09-02 18:05 ` David Singleton
2006-09-02 19:30 ` Rafael J. Wysocki
2006-09-03 16:25 ` David Singleton
2006-09-03 20:57 ` Rafael J. Wysocki
2006-09-03 21:33 ` Pavel Machek
2006-09-09 0:39 ` David Singleton
2006-09-09 0:48 ` David Singleton
2006-09-09 16:13 ` Pavel Machek
2006-09-09 12:17 ` Pavel Machek
2006-09-11 15:11 ` David Singleton
2006-09-11 17:14 ` Pavel Machek
2006-09-11 18:58 ` Matthew Locke
2006-08-30 4:52 ` David Singleton
2006-08-30 5:52 ` Matthew Locke
2006-08-30 13:39 ` Preece Scott-PREECE
2006-08-30 22:43 ` Pavel Machek
2006-08-27 19:48 ` Greg KH
2006-08-28 0:07 ` David Singleton
2006-08-27 20:54 ` Eugeny S. Mints
2006-08-28 22:18 ` Pavel Machek
2006-08-29 21:46 ` Eugeny S. Mints
2006-08-29 1:29 ` David Singleton
2006-08-29 22:39 ` Eugeny S. Mints
2006-08-31 13:27 ` Amit Kucheria
2006-08-31 19:22 ` Preece Scott-PREECE
2006-09-01 8:11 ` Amit Kucheria
2006-08-14 23:29 ` Dominik Brodowski
2006-08-14 23:48 ` Matthew Locke
-- strict thread matches above, loose matches on Subject: below --
2006-08-16 1:27 Scott E. Preece
2006-08-16 15:25 ` Mark Gross
2006-08-20 13:36 Woodruff, Richard
2006-08-23 19:20 Woodruff, Richard
2006-08-24 8:03 ` Pavel Machek
2006-08-24 12:16 Woodruff, Richard
2006-08-24 12:29 ` Pavel Machek
2006-08-24 14:52 Woodruff, Richard
2006-08-25 19:58 ` Pavel Machek
2006-08-25 20:05 Woodruff, Richard
2006-08-25 20:08 ` Pavel Machek
2006-08-25 20:22 Woodruff, Richard
2006-08-25 20:34 ` Alan Stern
2006-08-25 21:27 ` Pavel Machek
2006-08-25 21:46 ` Alan Stern
2006-08-25 22:03 ` Pavel Machek
2006-08-26 2:21 ` Alan Stern
2006-08-25 20:57 Woodruff, Richard
2006-08-25 21:13 ` Alan Stern
2006-08-25 21:21 Woodruff, Richard
2006-08-25 21:42 ` Alan Stern
2006-08-25 22:11 Woodruff, Richard
2006-08-31 0:52 Scott E. Preece
2006-08-31 2:41 Woodruff, Richard
2006-08-31 15:14 Scott E. Preece
2006-09-01 14:49 Scott E. Preece
2006-09-03 21:21 Scott E. Preece
2006-09-03 21:54 ` Pavel Machek
2006-09-03 21:34 Scott E. Preece
2006-09-03 21:43 ` Pavel Machek
2006-09-03 22:10 ` Rafael J. Wysocki
2006-09-03 22:12 Scott E. Preece
2006-09-03 22:25 ` Pavel Machek
2006-09-03 22:31 Scott E. Preece
2006-09-03 22:41 ` Pavel Machek
2006-09-03 22:40 Scott E. Preece
2006-09-04 9:06 ` Pavel Machek
2006-09-05 16:45 ` Mark Gross
2006-09-06 10:59 ` Pavel Machek
2006-09-03 23:00 Scott E. Preece
2006-09-04 9:12 ` Pavel Machek
2006-09-05 10:31 ` Rafael J. Wysocki
2006-09-03 23:05 Scott E. Preece
2006-09-04 9:09 ` Pavel Machek
2006-09-04 15:43 Scott E. Preece
2006-09-05 16:03 Scott E. Preece
2006-09-05 20:42 ` Rafael J. Wysocki
2006-09-06 10:56 ` Pavel Machek
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=20060830222714.GD3923@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-pm@lists.osdl.org \
--cc=mgross@linux.intel.com \
/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