From: Jon Brenner <jbrenner@taosinc.com>
To: linux-iio <linux-iio@vger.kernel.org>
Cc: Jonathan Cameron <jic23@cam.ac.uk>
Subject: [PATCH V1] RFC - Proposed IIO Documentation patch to add CCT and RGBC data
Date: Tue, 01 May 2012 16:27:34 -0500 [thread overview]
Message-ID: <1335907654.766.24.camel@jonz-ub2> (raw)
Request for Comments -
Documentation patch to add Correlated Color Temperature (CCT) and RGBC (red/green/blue/clear) data.
The addition of CCT and RGBC is afforded by utilizing a 'real channel' type of IIO_CCT, and 4 modifiers of IIO_MOD_LIGHT_CLEAR, IIO_MOD_LIGHT_RED, IIO_MOD_LIGHT_GREEN, and IIO_MOD_LIGHT_BLUE, found in types.h.
A trivial addition to industrialio-core.c is required.
in_cct0_input will return typically return the color temperature expressed in kelvins.
IIO_MODIFIERs are respective of the associated light frequencies for each of the channels.
Signed-off-by: Jon Brenner <jbrenner@taosinc.com>
---
.../staging/iio/Documentation/sysfs-bus-iio-light | 46 ++++++++++++++++++++
1 files changed, 46 insertions(+), 0 deletions(-)
diff --git a/drivers/staging/iio/Documentation/sysfs-bus-iio-light b/drivers/staging/iio/Documentation/sysfs-bus-iio-light
index 715c74d..bd42baf 100644
--- a/drivers/staging/iio/Documentation/sysfs-bus-iio-light
+++ b/drivers/staging/iio/Documentation/sysfs-bus-iio-light
@@ -34,6 +34,15 @@ Description:
it comes back in SI units, it should also include _input else it
should include _raw to signify it is not in SI units.
+What: /sys/bus/iio/devices/device[n]/in_cct0[_input|_raw]
+KernelVersion: 3.4.0
+Contact: linux-iio@vger.kernel.org
+Description:
+ This should return the correlated color temperature from the
+ light sensor. If it comes back in SI units, it should also
+ include _input else it should include _raw to signify it is not
+ in SI units.
+
What: /sys/.../device[n]/proximity_on_chip_ambient_infrared_supression
KernelVersion: 2.6.37
Contact: linux-iio@vger.kernel.org
@@ -82,3 +91,40 @@ Contact: linux-iio@vger.kernel.org
Description:
This property gets/sets the table of coefficients
used in calculating illuminance in lux.
+
+What: /sys/bus/iio/devices/device[n]/in_intensity_clear[_input|_raw]
+KernelVersion: 3.4.0
+Contact: linux-iio@vger.kernel.org
+Description:
+ This property is supported by sensors that have a RGBC
+ sensing mode. This value should be the output from a reading
+ and if expressed in SI units, should include _input. If this
+ value is not in SI units, then it should include _raw.
+
+What: /sys/bus/iio/devices/device[n]/in_intensity_red[_input|_raw]
+KernelVersion: 3.4.0
+Contact: linux-iio@vger.kernel.org
+Description:
+ This property is supported by sensors that have a RGBC
+ sensing mode. This value should be the output from a reading
+ and if expressed in SI units, should include _input. If this
+ value is not in SI units, then it should include _raw.
+
+What: /sys/bus/iio/devices/device[n]/in_intensity_green[_input|_raw]
+KernelVersion: 3.4.0
+Contact: linux-iio@vger.kernel.org
+Description:
+ This property is supported by sensors that have a RGBC
+ sensing mode. This value should be the output from a reading
+ and if expressed in SI units, should include _input. If this
+ value is not in SI units, then it should include _raw.
+
+What: /sys/bus/iio/devices/device[n]/in_intensity_blue[_input|_raw]
+KernelVersion: 3.4.0
+Contact: linux-iio@vger.kernel.org
+Description:
+ This property is supported by sensors that have a RGBC
+ sensing mode. This value should be the output from a reading
+ and if expressed in SI units, should include _input. If this
+ value is not in SI units, then it should include _raw.
+
--
1.7.4.1
next reply other threads:[~2012-05-01 21:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-01 21:27 Jon Brenner [this message]
2012-05-02 8:39 ` [PATCH V1] RFC - Proposed IIO Documentation patch to add CCT and RGBC data Jonathan Cameron
2012-05-11 7:48 ` Jonathan Cameron
2012-05-14 16:02 ` Jon Brenner
2012-05-14 17:38 ` Jonathan Cameron
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=1335907654.766.24.camel@jonz-ub2 \
--to=jbrenner@taosinc.com \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).