From: Pavel Machek <pavel@ucw.cz>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-acpi <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Len Brown <lenb@kernel.org>, Richard Purdie <rpurdie@rpsys.net>,
Matthew Garrett <mjg59@srcf.ucam.org>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH 0/3] Generic sysfs support for ACPI ALS and other ALS devices
Date: Tue, 4 Aug 2009 15:21:29 +0200 [thread overview]
Message-ID: <20090804132129.GH18974@elf.ucw.cz> (raw)
In-Reply-To: <1249290657.2670.250.camel@rzhang-dt>
On Mon 2009-08-03 17:10:57, Zhang Rui wrote:
> Hi, all,
>
> This is the patch set I made to introduce ACPI ALS device driver
> and a generic sysfs I/F for all the ALS devices, like ACPI ALS,
> platform ALS, etc.
>
> Patch 01 introduces the ACPI ALS device driver.
>
> Patch 02 introduces ALS sysfs class.
> Two sysfs I/F are created for each ALS device.
> /sys/class/als/alsX/illuminance:
> the amount of light incident upon a specified surface area.
> /sys/class/als/alsX/mappings:
> ambient light illuminance to display luminance mappings
> that can be used by an OS to calibrate its ambient light policy
> this is what I got on a test box:
> cat /sys/class/als/als0/mappings
> ???Illuminance Adjustment
> 0 70
> 10 73
> 80 85
> 300 100
> 1000 150
There's one value per file for sysfs... You should definitely have the
header.
Is there chance to already return adjusted values, avoiding this
uglyness?
Plus I'd say Documentation/ file is needed.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-08-04 13:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 9:10 [PATCH 0/3] Generic sysfs support for ACPI ALS and other ALS devices Zhang Rui
2009-08-04 1:12 ` ykzhao
2009-08-04 7:30 ` Zhang Rui
2009-08-04 13:21 ` Pavel Machek [this message]
2009-08-04 15:10 ` Greg KH
2009-08-04 17:24 ` Valdis.Kletnieks
2009-08-04 17:36 ` Greg KH
2009-08-05 1:04 ` Zhang Rui
2009-08-05 16:10 ` Valdis.Kletnieks
2009-08-06 1:51 ` Zhang Rui
2009-08-05 0:55 ` Zhang Rui
2009-08-05 1:02 ` Zhang Rui
2009-08-05 16:19 ` Pavel Machek
2009-08-06 1:41 ` Zhang Rui
2009-08-06 7:13 ` Pavel Machek
2009-08-06 8:47 ` Zhang Rui
2009-08-06 9:52 ` Pavel Machek
2009-08-17 8:32 ` Zhang Rui
2009-08-21 11:51 ` Pavel Machek
2009-08-25 1:13 ` Zhang Rui
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=20090804132129.GH18974@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=greg@kroah.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox