From: Richard Purdie <rpurdie@rpsys.net>
To: Zhang Rui <rui.zhang@intel.com>
Cc: Matthew Garrett <mjg@redhat.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 09:22:33 +0100 [thread overview]
Message-ID: <1247646153.6248.3.camel@dax.rpnet.com> (raw)
In-Reply-To: <1247644518.26272.88.camel@rzhang-dt>
On Wed, 2009-07-15 at 15:55 +0800, Zhang Rui wrote:
> > Also, are "userspace" and "kernel" as meaningful as they could be?
> Would
> > "sysfs" and "hwkeys" make more sense and allow for other future hardware
> > differences? Perhaps someone will tie the backlight to an ambient light
> > sensor for example...
> >
>
> Hah, I just finished a patch to introduce the ACPI als driver.
>
> I'm not quite familiar with the status of ALS support in Linux kernel.
> and here is my questions,
> I don't think we have a generic sysfs driver for ALS, i.e. ALS class
> device, right?
> do you guys think it's reasonable to have one?
We don't have one that I'm aware of.
The first question is what information and configuration options are we
likely to have with ALS sensors? If its just a light level reading, the
input subsystem is ideally suited for sharing that. Is there
configuration we need to expose?
Cheers,
Richard
--
Richard Purdie
Intel Open Source Technology Centre
next prev parent reply other threads:[~2009-07-15 8:26 UTC|newest]
Thread overview: 27+ 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 [this message]
2009-07-15 8:38 ` Zhang Rui
2009-07-15 9:11 ` Richard Purdie
2009-07-15 13:58 ` Matthew Garrett
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-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=1247646153.6248.3.camel@dax.rpnet.com \
--to=rpurdie@rpsys.net \
--cc=corentincj@iksaif.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox