From: Pavel Machek <pavel@ucw.cz>
To: Dmitry Krivoschekov <dmitry.krivoschekov@gmail.com>
Cc: linux-pm <linux-pm@lists.osdl.org>
Subject: Re: [RFC] dynamic device power management proposal
Date: Wed, 21 Mar 2007 23:54:29 +0100 [thread overview]
Message-ID: <20070321225429.GK6057@elf.ucw.cz> (raw)
In-Reply-To: <4601A87F.6040608@gmail.com>
On Thu 2007-03-22 00:49:51, Dmitry Krivoschekov wrote:
> Amit Kucheria wrote:
> > On 3/21/07, Shaohua Li <shaohua.li@intel.com> wrote:
> >> On Wed, 2007-03-21 at 02:30 +0800, Pavel Machek wrote:
> >
> >>> No, that's not how it works; look at hda_audio, it already has
> >>> powersave. Just power down audio card 5 seconds after its control file
> >>> is closed.
> >> It's another case of doing policy in a driver.
> >>
> >
> > IMHO, this kind of policy is best handled inside the driver because it
> > is specific to the hardware. This will ensure that the driver will
> > just work on every distro without some userspace policy being present
> > and setup _correctly_.
>
> It some circumstances this policy may increase power consumption
> but not decrease it. Consider the case of repeatable operation,
And what... that happens. Lets not break our design because you can
think of very contrieved corner case.
> something like periodic sound beep, with period of 5s.
> In this case, a driver implementing the policy will periodically
> suspend/resume a number of devices - audio controller, codec, ADC,
> but the operation itself (suspending/resuming) will consume
> more power than power consumed by these devices in case they
> left running for a 5s. In such a case you may want to change
> the predefined value or just disable the policy.
> Yes, we may just not close a sound device file, but phone
> applications I've seen, do close the file.
Fix the app, then.
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:[~2007-03-21 22:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 9:08 [RFC] dynamic device power management proposal Shaohua Li
2007-03-19 15:44 ` Alan Stern
2007-03-20 1:06 ` Shaohua Li
2007-03-20 14:58 ` Alan Stern
2007-03-21 1:43 ` Shaohua Li
2007-03-21 14:44 ` Alan Stern
2007-03-22 4:42 ` Len Brown
2007-03-22 11:56 ` Jim Gettys
2007-03-22 19:28 ` David Brownell
2007-03-22 13:20 ` Pavel Machek
2007-03-22 13:44 ` Oliver Neukum
2007-03-22 13:56 ` Pavel Machek
2007-03-22 14:18 ` Oliver Neukum
2007-03-22 14:22 ` Pavel Machek
2007-03-22 14:26 ` Oliver Neukum
2007-03-22 14:35 ` Pavel Machek
2007-03-22 19:41 ` David Brownell
2007-03-22 19:58 ` David Brownell
2007-03-20 18:30 ` Pavel Machek
2007-03-21 1:34 ` Shaohua Li
2007-03-21 15:21 ` Amit Kucheria
2007-03-21 21:49 ` Dmitry Krivoschekov
2007-03-21 22:54 ` Pavel Machek [this message]
2007-03-21 21:39 ` Pavel Machek
2007-03-22 3:09 ` Shaohua Li
2007-03-22 13:13 ` Pavel Machek
2007-03-22 19:20 ` David Brownell
2007-03-22 20:32 ` Alan Stern
2007-03-22 20:02 ` David Brownell
2007-03-22 22:10 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2007-03-21 20:19 Scott E. Preece
2007-03-21 21:45 ` Pavel Machek
2007-03-26 13:53 ` Amit Kucheria
2007-03-22 13:39 Scott E. Preece
2007-03-22 13:48 ` Oliver Neukum
2007-03-22 14:01 ` Pavel Machek
2007-03-22 14:45 ` Alan Stern
2007-03-22 18:53 ` David Brownell
2007-03-22 19:05 Scott E. Preece
2007-03-27 12:05 ` Pavel Machek
2007-03-27 12:19 ` Oliver Neukum
2007-03-22 19:18 Scott E. Preece
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=20070321225429.GK6057@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=dmitry.krivoschekov@gmail.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