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.0906072309560.28801-100000@netrider.rowland.org>
Date:	Sun, 7 Jun 2009 23:10:52 -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 11:03:48PM -0400, Alan Stern wrote:
> 
> > 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.
> 
> There's a lot of power management situations where you don't end up with 
> the optimal power configuration until a driver's bound. It's certainly 
> possible to do this in userspace, but if we know that the hardware 
> supported by a given driver will always work then it seems reasonable to 
> have it whitelist autosuspend on that device.

Sure.  Such a thing could be added easily enough.  It just doesn't 
exist now, that's all.

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/