From: Zhang Rui <rui.zhang@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Len Brown <lenb@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>, Greg KH <greg@kroah.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH V6 2/2] introduce ACPI ALS device driver
Date: Tue, 01 Sep 2009 16:39:36 +0800 [thread overview]
Message-ID: <1251794376.3483.238.camel@rzhang-dt> (raw)
In-Reply-To: <20090901081342.GB9942@elf.ucw.cz>
On Tue, 2009-09-01 at 16:13 +0800, Pavel Machek wrote:
> Hi!
>
> > ACPI spec defines ACPI Ambient Light Sensor device (hid ACPI0008),
> > which provides a standard interface by which the OS may query properties
> > of the ambient light environment the system is currently operating in,
> > as well as the ability to detect meaningful changes in these values when
> > the environment changes.
>
> > +struct acpi_als {
> > + struct acpi_device *device;
> > + struct als_device *als_sys;
> > + int illuminance;
> > + int chromaticity;
> > + int temperature;
> > + int polling;
> > + int count;
> > + struct als_mapping *mappings;
> > +};
>
> chromaticity is write-only variable.
> I believe you can drop it and
> associted code.
>
> temperature ditto. Drop from this version?
>
> polling ditto. Drop from this version?
>
color temperature, chromaticity and polling are three optional features
defined in the ACPI spec, which are not supported yet in the ACPI ALS
driver right now.
I think it's okay to add the code first and then generate some
incremental patches to enable these features once we found such kind of
platforms.
thanks,
rui
> Thanks,
> Pavel
next prev parent reply other threads:[~2009-09-01 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 7:25 Zhang Rui
2009-09-01 8:13 ` Pavel Machek
2009-09-01 8:39 ` Zhang Rui [this message]
2009-09-01 8:44 ` Pavel Machek
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=1251794376.3483.238.camel@rzhang-dt \
--to=rui.zhang@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=greg@kroah.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®