From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jon Brenner <jbrenner@TAOSinc.com>
Cc: jic23@kernel.org, gregkh@linuxfoundation.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Proposed addition to 'IIO interface' for color light sensing devices
Date: Wed, 04 Apr 2012 09:39:31 +0100 [thread overview]
Message-ID: <4F7C08C3.7090603@cam.ac.uk> (raw)
In-Reply-To: <B4B07CCC7B7A084E989CF9386538EA1D0120B3B3@exchsrvr.taosinc.com>
Not sure who else would be interested in this discussion so if anyone can cc
any interested parties that would be great! (
> I would like to propose the following addition to the 'IIO device
> interface' for color light sensing devices to accommodate CCT (AKA color
> temperature) and access to the raw RGB channel data for user analysis.
>
> IIO channel type name: CCT
>
> The CCT ABI should be documented similar to as follows:
> In sys-bus-iio-light:
> What: /sys/bus/iio/devices/device[n]/cct[_input|_raw]
> KernelVersion: 3.3.0
> Contact: linux-iio@vger.kernel.org
> Description:
> This should return the correlated color temperature from
> the RGBC color sensor
> expressed as SI unit (degree kelvin).
> 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.
Works for me though the formatting of the above is somewhat different from
our current docs...
>
> IIO modifiers:
> IIO_MOD_LIGHT_RED
> IIO_MOD_LIGHT_GREEN
> IIO_MOD_LIGHT_BLUE
So these modifiers apply to intensity channels? Colour temp is built from
multiple raw sensors I believe (like illuminance is often done?)
Hence it's another 'virtual' channel we compute?
>
> The 'clear' and IR channels are already covered by the use of IIO_LIGHT
> and IIO ILLUMINANCE (and respective modifiers).
> The RGB modifiers will help to express the relative frequencies to their
> respective channel, and appear to fit well with the overall convention.
>
> And last but not least, the textual modifier names "red", "green", and
> "blue" be accommodated within 'industrialio-core'.
Fine with me.
>
> Channel specific interrupt event / sources are not presented at this
> time.
>
> Any thoughts or comments are welcomed.
>
> Jon Brenner
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-04-04 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 23:04 Proposed addition to 'IIO interface' for color light sensing devices Jon Brenner
2012-04-04 8:39 ` Jonathan Cameron [this message]
2012-04-04 15:06 ` Jon Brenner
2012-04-04 16:17 ` Jonathan Cameron
2012-04-04 16:17 ` 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=4F7C08C3.7090603@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jbrenner@TAOSinc.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.