From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Corentin Chary <corentin.chary@gmail.com>,
acpi4asus-user@lists.sourceforge.net, len.brown@intel.com,
linux-kernel@vger.kernel.org,
USB list <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] eeepc-laptop: enable camera by default
Date: Fri, 05 Jun 2009 16:08:37 +0100 [thread overview]
Message-ID: <4A2934F5.4050601@tuffmail.co.uk> (raw)
In-Reply-To: <4A2931F5.1090709@tuffmail.co.uk>
Alan Jenkins wrote:
> Pekka Enberg wrote:
>> Hi Alan,
>>
>> On Fri, 2009-06-05 at 15:38 +0100, Alan Jenkins wrote:
>>
>>> Ok. I didn't bother shutting down my system, but I get a similar
>>> difference; 16 wakeups/s disabled v.s. 25 enabled. Anecdotally,
>>> disabling the camera does help battery life, and presumably Asus had
>>> good reason to implement it! (The shipped OS "fixes" the usability
>>> problem by patching the camera apps).
>>>
>>> BUT I found that autosuspend didn't seem to break anything, and
>>> enabling it also got me down to 16 wakeups/s. I think this is ideal
>>> because autosuspend is automatic so I can save power without manual
>>> toggling.
>>>
>>> Here's some magic to enable autosuspend:
>>>
>>> # echo -n auto > /sys/bus/usb/drivers/uvcvideo/*:*/../power/level
>>>
>>> Ideally this wants to be enabled automatically using a udev rule.
>>>
>>
>> Can the kernel do this by default for this specific driver on eeepc?
>>
>> Pekka
>>
>>
>
> Auto-suspend white-listing would be done on the basis of USB ids
> (vendor, product). At the moment it's expected that userspace should
> take ownership of it. There's no infrastructure for in-kernel
> whitelisting. I think.
>
> Large lists in udev rules can work, there are already lists of USB
> devices to set permissions for libusb access, e.g. for libmtp.
>
> [CC usb list - in the hope someone will point out if I got this wrong
> :-)]
>
> Alan
Btw I've now tested the udev rule, you can just dump this in a new
.rules file under /etc/udev/rules.d:
SUBSYSTEM=="usb", ATTR{idVendor}=="eb1a", ATTR{idProduct}=="2761", ATTR{power/level}="auto"
Not sure who I should submit it to though :-). debian-eeepc would take
it, but perhaps it should go in udev's default rules.
Regards
Alan
next prev parent reply other threads:[~2009-06-05 15: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 [this message]
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
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=4A2934F5.4050601@tuffmail.co.uk \
--to=alan-jenkins@tuffmail.co.uk \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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