mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Jenkins <sourcejedi.lkml@googlemail.com>
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
Subject: Re: [PATCH] eeepc-laptop: enable camera by default
Date: Fri, 5 Jun 2009 15:38:08 +0100	[thread overview]
Message-ID: <9b2b86520906050738kea062c9n1b2c0e767d6eb0aa@mail.gmail.com> (raw)
In-Reply-To: <1244209873.23533.29.camel@penberg-laptop>

On 6/5/09, Pekka Enberg <penberg@cs.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

  parent reply	other threads:[~2009-06-05 14:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05  8:59 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 [this message]
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
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=9b2b86520906050738kea062c9n1b2c0e767d6eb0aa@mail.gmail.com \
    --to=sourcejedi.lkml@googlemail.com \
    --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=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

all inboxes | Powered by JetHome®