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: <Pine.LNX.4.44L0.0906072256190.28801-100000@netrider.rowland.org>
Date:	Sun, 7 Jun 2009 23:03:48 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Matthew Garrett <mjg59@...f.ucam.org>
cc:	alan-jenkins@...fmail.co.uk, Pekka Enberg <penberg@...helsinki.fi>,
	Corentin Chary <corentin.chary@...il.com>,
	<acpi4asus-user@...ts.sourceforge.net>, <len.brown@...el.com>,
	<linux-kernel@...r.kernel.org>, <linux-usb@...r.kernel.org>,
	Darren Salt <linux@...mustbejoking.demon.co.uk>
Subject: Re: [PATCH] eeepc-laptop: enable camera by default

On Mon, 8 Jun 2009, Matthew Garrett wrote:

> On Sun, Jun 07, 2009 at 04:41:30PM +0100, Alan Jenkins wrote:
> 
> > Hmm, some cameras have input devices (i.e. buttons). In fact, uvcvideo
> > registers an input device on my EEE even though it has no buttons.  I
> > think that needs investigating :-(.
> > 
> > It's quite likely that the buttons can stop working when suspended.
> > And there might be other devices with the same IDs, which have a
> > button wired up.
> 
> A change has recently been committed that results in the button only 
> working if the v4l device is open. Otherwise you've got several wakeups 
> a second due to the polling of the button endpoint. I'm assuming that 
> opening the device disables autosuspend, so I wouldn't worry about that.
> 
> It'd be interesting to try enabling autosuspend on all UVC devices. Can 
> a driver indicate that its hardware supports it?

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.

Alan Stern

--
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/