linux-kernel - Re: [PATCH 1/3] backlight: Allow drivers to update the core, and generate events on changes

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: <1247711974.26272.190.camel@rzhang-dt>
Date:	Thu, 16 Jul 2009 10:39:34 +0800
From:	Zhang Rui <rui.zhang@...el.com>
To:	Matthew Garrett <mjg59@...f.ucam.org>
Cc:	Richard Purdie <rpurdie@...ys.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"lenb@...nel.org" <lenb@...nel.org>,
	"corentincj@...aif.net" <corentincj@...aif.net>
Subject: Re: [PATCH 1/3] backlight: Allow drivers to update the core, and
	generate events on changes

On Wed, 2009-07-15 at 21:58 +0800, Matthew Garrett wrote:
> On Wed, Jul 15, 2009 at 10:11:29AM +0100, Richard Purdie wrote:
> 
> > So there are basically two values we're ever interested in at a given
> > point in time. The current ambient light reading and the corresponding
> > display luminance adjustment. Both of those could just be exposed as an
> > input device really?
> 
> The alternative would be hwmon, I guess.

you mean convert an ACPI ALS device to a hwmon device?

> 
> > Agreed, userspace should be where policy is decided. Having a standalone
> > module which connected the two together with a "default" policy might be
> > acceptable too though? If userspace then wants to handle things it just
> > makes sure the module is not loaded.
> 
> You want smoothing even in a default policy, and doing that well might 
> be a bit much for the kernel?
> 
sorry, I don't understand.
do you mean that there should be a default policy in the kernel?

thanks,
rui

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