public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <sourcejedi.lkml@googlemail.com>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: Woody Suwalski <woodys@xandros.com>,
	Pekka J Enberg <penberg@cs.helsinki.fi>,
	acpi4asus-user@lists.sourceforge.net, len.brown@intel.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] eeepc-laptop: enable camera by default
Date: Sat, 6 Jun 2009 09:04:20 +0100	[thread overview]
Message-ID: <9b2b86520906060104q62ebdfcdv7af63cf1dee416db@mail.gmail.com> (raw)
In-Reply-To: <71cd59b00906060012w6bc6f302o76fea3c8a570840e@mail.gmail.com>

On 6/6/09, Corentin Chary <corentin.chary@gmail.com> wrote:
> On Fri, Jun 5, 2009 at 11:01 PM, Woody Suwalski<woodys@xandros.com> wrote:
>> Corentin Chary wrote:
>>>
>>> On Fri, Jun 5, 2009 at 10:59 AM, Pekka J Enberg<penberg@cs.helsinki.fi>
>>> wrote:
>>>
>>>>
>>>> From: Pekka Enberg <penberg@cs.helsinki.fi>
>>>>
>>>> If we leave the camera disabled by default, userspace programs (e.g.
>>>> Skype, Cheese) leave the user out in the cold saying that the machine
>>>> "has
>>>> no camera." Therefore, it's better to enable camera by default and let
>>>> people who really don't want it just disable the thing.
>>>>
>>>> Cc: <acpi4asus-user@lists.sourceforge.net>
>>>> Cc: Len Brown <len.brown@intel.com>
>>>> Signed-off-by: Pekka Enberg <penberg@cs.helsinki.fi>
>>>> ---
>>>>  drivers/platform/x86/eeepc-laptop.c |   16 ++++++++++++++++
>>>>  1 files changed, 16 insertions(+), 0 deletions(-)
>>>>
>>>> diff --git a/drivers/platform/x86/eeepc-laptop.c
>>>> b/drivers/platform/x86/eeepc-laptop.c
>>>> index 353a898..c0f8eb1 100644
>>>> --- a/drivers/platform/x86/eeepc-laptop.c
>>>> +++ b/drivers/platform/x86/eeepc-laptop.c
>>>> @@ -334,6 +334,19 @@ static int eeepc_bluetooth_rfkill_state(void *data,
>>>> enum rfkill_state *state)
>>>>  }
>>>>
>>>>  /*
>>>> + * Camera helpers
>>>> + */
>>>> +
>>>> +static void eeepc_enable_camera(void)
>>>> +{
>>>> +       int err;
>>>> +
>>>> +       err = set_acpi(CM_ASL_CAMERA, 1);
>>>> +       if (err)
>>>> +               printk(EEEPC_WARNING "Unable to enable camera %d\n",
>>>> err);
>>>> +}
>>>> +
>>>> +/*
>>>>  * Sys helpers
>>>>  */
>>>>  static int parse_arg(const char *buf, unsigned long count, int *val)
>>>> @@ -996,6 +1009,9 @@ static int __init eeepc_laptop_init(void)
>>>>       result = eeepc_hwmon_init(dev);
>>>>       if (result)
>>>>               goto fail_hwmon;
>>>> +
>>>> +       eeepc_enable_camera();
>>>> +
>>>>       /* Register platform stuff */
>>>>       result = platform_driver_register(&platform_driver);
>>>>       if (result)
>>>> --
>>>> 1.5.6.3
>>>>
>>>>
>>>>
>>>
>>> Hi,
>>> First, I think a one line
>>> set_acpi(CM_ASL_CAMERA, 1);
>>> with a small comment is better. (If it fails, it's because there no
>>> camera, so we don't mind).
>>>
>>> Anyway, I'm not sure it's a good idea to enable the camera by default.
>>> It depends how many
>>> power the camera is using (when idle). Coud you check that (with power
>>> top maybe ?).
>>>
>>> Thanks
>>>
>>
>> From our old measurements:
>>
>> idle camera is ~20mA out of ~650mA total power... (measured on 901 model).
>>
>> Woody
>>
>> --
>> Woody Suwalski, Xandros, Ottawa, Canada, 1-613-842-3498 x414
>>
>>
>
> Do also have some results with
> echo -n auto > /sys/bus/usb/drivers/uvcvideo/*:*/../power/level
>
> ?

Can I also ask if you tested with

CONFIG_NO_HZ=y

?  IIRC, the kernel shipped on my old Eee didn't have NOHZ.  Without
NOHZ, it won't save much _cpu_ power; cutting 10 wakeups/s off >100
won't make much difference.

Ta
Alan

  reply	other threads:[~2009-06-06  8:04 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
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 [this message]
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=9b2b86520906060104q62ebdfcdv7af63cf1dee416db@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 \
    --cc=woodys@xandros.com \
    /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