From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: alan-jenkins@tuffmail.co.uk,
Pekka Enberg <penberg@cs.helsinki.fi>,
Corentin Chary <corentin.chary@gmail.com>,
acpi4asus-user@lists.sourceforge.net, len.brown@intel.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Darren Salt <linux@youmustbejoking.demon.co.uk>
Subject: Re: [PATCH] eeepc-laptop: enable camera by default
Date: Mon, 8 Jun 2009 04:07:32 +0100 [thread overview]
Message-ID: <20090608030732.GA7018@srcf.ucam.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0906072256190.28801-100000@netrider.rowland.org>
On Sun, Jun 07, 2009 at 11:03:48PM -0400, Alan Stern wrote:
> There's no mechanism for this. It many environments it couldn't work,
> because the decision about whether to enable autosuspend is made when
> the device is first created (i.e., when the creation uevent is
> received), whereas driver binding doesn't occur until later.
There's a lot of power management situations where you don't end up with
the optimal power configuration until a driver's bound. It's certainly
possible to do this in userspace, but if we know that the hardware
supported by a given driver will always work then it seems reasonable to
have it whitelist autosuspend on that device.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-06-08 3:07 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 8:59 [PATCH] eeepc-laptop: enable camera by default Pekka J Enberg
2009-06-05 11:46 ` Corentin Chary
2009-06-05 12:44 ` Pekka Enberg
2009-06-05 13:02 ` Corentin Chary
2009-06-05 13:39 ` Alan Jenkins
2009-06-05 13:51 ` Pekka Enberg
2009-06-05 13:54 ` Pekka Enberg
2009-06-05 13:58 ` Corentin Chary
2009-06-05 14:38 ` Alan Jenkins
2009-06-05 14:50 ` Pekka Enberg
2009-06-05 14:55 ` Alan Jenkins
2009-06-05 15:08 ` Alan Jenkins
2009-06-05 15:14 ` Pekka Enberg
2009-06-07 14:54 ` Darren Salt
2009-06-07 15:41 ` Alan Jenkins
2009-06-07 23:28 ` Matthew Garrett
2009-06-08 3:03 ` Alan Stern
2009-06-08 3:07 ` Matthew Garrett [this message]
2009-06-08 3:10 ` Alan Stern
2009-06-08 15:00 ` Matthew Garrett
2009-06-08 20:44 ` Alan Stern
2009-06-05 15:13 ` Alan Stern
2009-06-05 15:22 ` Pekka Enberg
2009-06-05 21:01 ` Woody Suwalski
2009-06-06 7:12 ` Corentin Chary
2009-06-06 8:04 ` Alan Jenkins
2009-06-05 20:08 ` Andrew Morton
2009-06-06 7:25 ` Corentin Chary
2009-06-06 7:31 ` Andrew Morton
2009-06-06 7:52 ` Corentin Chary
2009-06-06 9:17 ` Pekka Enberg
2009-06-06 10:17 ` Corentin Chary
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=20090608030732.GA7018@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=corentin.chary@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@youmustbejoking.demon.co.uk \
--cc=penberg@cs.helsinki.fi \
--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