From: Pavel Machek <pavel@ucw.cz>
To: Oliver Neukum <oliver@neukum.org>
Cc: David Brownell <david-b@pacbell.net>,
Alan Stern <stern@rowland.harvard.edu>,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: /sys/.../power/state Re: [linux-usb-devel] error to be returned while suspended
Date: Sun, 8 Oct 2006 21:41:24 +0200 [thread overview]
Message-ID: <20061008194124.GB4042@elf.ucw.cz> (raw)
In-Reply-To: <200610081524.09946.oliver@neukum.org>
Hi!
> > > The power management functions without
> > > timeout are also exported. For other power control features like
> > > cpu frequency considerable effort has been made to export them to
> > > user space.
> >
> > Yes, and many of us use the much lighter weight kernel based control
> > models by preference. Why waste hundreds of Kbytes of userspace for
> > a daemon when a few hundred bytes of kernel code can implement a
> > better and more reactive kernel policy for cpufreq?
>
> That's an important aspect. How about implementing autosuspend
> first and keeping the sysfs-based suspension for now? If autosuspend
Current sysfs-based suspension allows people to do bad stuff to
drivers, like confusing them, oopsing them, etc. It is so broken that
it can not be fixed. (When I suspend my USB this way, I end up with
dead USB. When I suspend my sound card, I get any soundcard users in
unrecoverable D state.)
Now... you can prove me wrong, but that likely means auditing all the
drivers with suspend() and/or resume() methods. I'm not prepared to do
that work... are you?
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-10-08 19:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 11:23 Oliver Neukum
2006-10-03 12:51 ` linux-os (Dick Johnson)
2006-10-03 13:02 ` Oliver Neukum
2006-10-03 14:17 ` linux-os (Dick Johnson)
2006-10-04 11:19 ` Pavel Machek
2006-10-04 16:34 ` Oliver Neukum
2006-10-04 22:44 ` Pavel Machek
2006-10-05 7:07 ` Oliver Neukum
2006-10-05 8:57 ` Pavel Machek
2006-10-05 16:21 ` [linux-usb-devel] " Alan Stern
2006-10-05 16:35 ` Oliver Neukum
2006-10-05 18:24 ` Alan Stern
2006-10-05 18:43 ` Oliver Neukum
2006-10-05 20:48 ` Alan Stern
2006-10-05 21:25 ` Oliver Neukum
2006-10-05 21:45 ` Alan Stern
2006-10-06 7:21 ` Oliver Neukum
2006-10-06 17:48 ` Alan Stern
2006-10-06 11:25 ` Pavel Machek
2006-10-06 2:47 ` David Brownell
2006-10-06 7:04 ` Oliver Neukum
2006-10-06 11:27 ` Pavel Machek
2006-10-06 14:09 ` Oliver Neukum
2006-10-06 21:10 ` David Brownell
2006-10-07 10:49 ` Oliver Neukum
2006-10-07 11:08 ` Pavel Machek
2006-10-07 17:16 ` Oliver Neukum
2006-10-08 0:03 ` David Brownell
2006-10-08 2:03 ` Alan Stern
2006-10-08 7:07 ` Oliver Neukum
2006-10-08 14:27 ` Alan Stern
2006-10-08 19:36 ` Pavel Machek
2006-10-08 19:57 ` Oliver Neukum
2006-10-08 21:06 ` Pavel Machek
2006-10-08 6:40 ` Oliver Neukum
2006-10-09 15:56 ` David Brownell
2006-10-08 6:51 ` Oliver Neukum
2006-10-08 7:14 ` Oliver Neukum
2006-10-08 13:24 ` Oliver Neukum
2006-10-08 14:32 ` Alan Stern
2006-10-08 19:41 ` Pavel Machek [this message]
2006-10-08 19:19 ` Pavel Machek
[not found] ` <200610080838.03488.oliver@neukum.org>
[not found] ` <200610080020.49158.david-b@pacbell.net>
2006-10-08 8:39 ` Oliver Neukum
2006-10-08 14:16 ` Dmitry Torokhov
2006-10-06 11:23 ` Pavel Machek
2006-10-06 11:21 ` 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=20061008194124.GB4042@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oliver@neukum.org \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®