[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1247646153.6248.3.camel@dax.rpnet.com>
Date: Wed, 15 Jul 2009 09:22:33 +0100
From: Richard Purdie <rpurdie@...ys.net>
To: Zhang Rui <rui.zhang@...el.com>
Cc: Matthew Garrett <mjg@...hat.com>,
"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 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
--
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/
Powered by blists - more mailing lists