From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Richard Purdie <rpurdie@rpsys.net>
Cc: Zhang Rui <rui.zhang@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"lenb@kernel.org" <lenb@kernel.org>,
"corentincj@iksaif.net" <corentincj@iksaif.net>
Subject: Re: [PATCH 1/3] backlight: Allow drivers to update the core, and generate events on changes
Date: Wed, 15 Jul 2009 14:58:08 +0100 [thread overview]
Message-ID: <20090715135808.GA19054@srcf.ucam.org> (raw)
In-Reply-To: <1247649089.20241.5.camel@dax.rpnet.com>
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.
> 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?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-07-15 13:58 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 20:41 [PATCH 1/3] backlight: Allow drivers to update the core, and generate events on changes Matthew Garrett
2009-07-13 20:41 ` [PATCH 2/3] ACPI: Update the backlight state when we change brightness Matthew Garrett
2009-07-13 20:41 ` [PATCH 3/3] eeepc-laptop: " Matthew Garrett
2009-07-14 0:58 ` [PATCH 1/3] backlight: Allow drivers to update the core, and generate events on changes ykzhao
2009-07-14 1:53 ` Matthew Garrett
2009-07-14 15:48 ` Matthew Garrett
2009-07-14 10:30 ` Henrique de Moraes Holschuh
2009-07-14 13:21 ` Matthew Garrett
2009-07-14 15:54 ` Henrique de Moraes Holschuh
2009-07-14 12:29 ` Richard Purdie
2009-07-14 12:55 ` Matthew Garrett
2009-07-15 7:55 ` Zhang Rui
2009-07-15 8:22 ` Richard Purdie
2009-07-15 8:38 ` Zhang Rui
2009-07-15 9:11 ` Richard Purdie
2009-07-15 13:58 ` Matthew Garrett [this message]
2009-07-16 2:39 ` Zhang Rui
2009-07-16 2:40 ` Matthew Garrett
2009-07-29 15:05 ` Pavel Machek
2009-07-29 15:20 ` Matthew Garrett
2009-07-29 15:31 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2009-07-14 16:06 Matthew Garrett
2009-07-16 21:33 ` Michal Schmidt
2009-07-16 21:33 ` Michal Schmidt
2009-07-18 11:48 ` Pavel Machek
2009-09-19 23:24 ` Henrique de Moraes Holschuh
2009-09-20 4:15 ` Matthew Garrett
2009-09-20 11:16 ` Henrique de Moraes Holschuh
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=20090715135808.GA19054@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=corentincj@iksaif.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=rui.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.