From: Pavel Machek <pavel@ucw.cz>
To: "Scott E. Preece" <preece@motorola.com>
Cc: linux-pm@lists.osdl.org
Subject: Re: [RFC] dynamic device power management proposal
Date: Tue, 27 Mar 2007 14:05:43 +0200 [thread overview]
Message-ID: <20070327120543.GF5161@elf.ucw.cz> (raw)
In-Reply-To: <200703221905.l2MJ5VEU017196@olwen.urbana.css.mot.com>
Hi!
> | > And latency may be ignorable in a laptop environment, but it absolutely
> | > isn't in embedded devices, which users expect to operate immediately, as
> | > though they were gear-driven rather than computer-driven.
> |
> | What latency are you talking about? Powering up piece of hw takes one
> | milisecond or something. If your /dev/dsp takes 3 seconds to power up,
> | you probably need userspace policy daemon. But that is not the case,
> | hw takes few miliseconds to wake up.
>
> Sure, but *some* devices take substantially longer to power up or
> down. If you insist that the driver should make the power down
> decision, then you lump high-latency and low-latency devices together,
> even though high-latency devices might be better served by separating
> the semantics.
High-latency devices indeed may be served better by separating the
semantics. Fortunately the high-latency (we are talking >50msec here,
right?) are rare enough... Like "none" in most embedded
systems... Actually only common high-latency device is harddrive
(spinup/spindown), and that's already handled specially with userspace
hooks.
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-27 12:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 19:05 [RFC] dynamic device power management proposal Scott E. Preece
2007-03-27 12:05 ` Pavel Machek [this message]
2007-03-27 12:19 ` Oliver Neukum
-- strict thread matches above, loose matches on Subject: below --
2007-03-22 19:18 Scott E. Preece
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-21 20:19 Scott E. Preece
2007-03-21 21:45 ` Pavel Machek
2007-03-26 13:53 ` Amit Kucheria
2007-03-19 9:08 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
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
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=20070327120543.GF5161@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-pm@lists.osdl.org \
--cc=preece@motorola.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.