linux-kernel - Re: [PATCH] eeepc-laptop: enable camera by default

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <9b2b86520906050738kea062c9n1b2c0e767d6eb0aa@mail.gmail.com>
Date:	Fri, 5 Jun 2009 15:38:08 +0100
From:	Alan Jenkins <sourcejedi.lkml@...glemail.com>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	Corentin Chary <corentin.chary@...il.com>,
	acpi4asus-user@...ts.sourceforge.net, len.brown@...el.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] eeepc-laptop: enable camera by default

On 6/5/09, Pekka Enberg <penberg@...helsinki.fi> wrote:
> Hi Corentin,
>
> On Fri, 2009-06-05 at 15:02 +0200, Corentin Chary wrote:
>> > That said, I am more than happy to measure this but I need a little bit
>> > more information to get started as I have never used powertop. So what
>> > is it exactly you want me to do?
>>

>> For propers results, shutdown all services and just keep a shell
>> (without X or network).
>> You can also test that with and without the camera driver.
>
> I did not see a power usage estimate. I am running PowerTOP 1.11 that
> comes with Ubuntu 9.04. So I am not sure if what I did is what you
> wanted me to do but I ran "powertop -t 60 -d" with camera enabled and
> disabled and here are the results.

Yeah, "no ACPI power usage estimate available", just like my eeepc.

> Also, when I run plain powertop, it keeps complaining that some USB
> device causes wakeups (probably the camera?) and suggests suspending.
> But doing that doesn't seem to help things.

/me hijacks thread

Unfortunately powertop is out of date now.  The default behaviour is
not to suspend and it must be enabled on a per-device basis, because
there's lots of buggy hardware.

> Camera Disabled
> ---------------

> Wakeups-from-idle per second :  1.2	interval: 60.0s

> Camera Enabled
> --------------

> Wakeups-from-idle per second : 11.1	interval: 60.0s

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.

Anyway, my point is we should be happy to enable the camera by
default, because it will encourage the development of userspace
autosuspend whitelists :-).

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/