[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200508161635.00006cd2@Huawei.com>
Date: Fri, 8 May 2020 16:16:35 +0100
From: Jonathan Cameron <Jonathan.Cameron@...wei.com>
To: Gwendal Grignou <gwendal@...omium.org>
CC: <enric.balletbo@...labora.com>, <jic23@...nel.org>,
<bleung@...omium.org>, <groeck@...omium.org>,
<linux-kernel@...r.kernel.org>, <linux-iio@...r.kernel.org>
Subject: Re: [PATCH v2 1/3] iio: Add in_illumincance vectors in different
color spaces
On Wed, 6 May 2020 16:03:22 -0700
Gwendal Grignou <gwendal@...omium.org> wrote:
Illuminance in the title. Plus I'm still arguing these
aren't illuminance values.
The Y value is illuminance but X and Z definitely aren't.
RGB needs to stick to intensity - like the other existing
RGB sensors.
Gah. XYZ and IIO is a mess.
I suppose we could introduce a new type and have
in_illumiance_raw
in_chromacity_x_raw
in_chromacity_z_raw but chances of anyone understanding what we
are on about without reading wikipedia is low...
Sigh. Unless someone else chips in, I'm inclined to be lazy and rely
on documentation to let in_illuminance_x,y,z be defined as being
cie xyz color space measurements.
It seems slighlty preferable to defining another type for these,
though I suspect I'll regret this comment when some adds
cie lab which was always my favourite colour space :)
> Define 2 spaces for defining color coming from color sensors:
> RGB and XYZ: Both are in lux.
> RGB is the raw output from sensors (Red, Green and Blue channels), in
> addition to the existing clear channel (C).
> The RGBC vector goes through a matrix transformation to produce the XYZ
> vector. Y is illumincance, and XY caries the chromaticity information.
> The matrix is model specific, as the color sensor can be behing a glass
> that can filter some wavelengths.
>
> Signed-off-by: Gwendal Grignou <gwendal@...omium.org>
> ---
> New in v2.
>
> Documentation/ABI/testing/sysfs-bus-iio | 27 +++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
> index d3e53a6d8331b..256db6e63a25e 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio
> +++ b/Documentation/ABI/testing/sysfs-bus-iio
> @@ -1309,6 +1309,33 @@ Description:
> Illuminance measurement, units after application of scale
> and offset are lux.
>
> +What: /sys/.../iio:deviceX/in_illuminance_red_raw
> +What: /sys/.../iio:deviceX/in_illuminance_green_raw
> +What: /sys/.../iio:deviceX/in_illuminance_blue_raw
> +KernelVersion: 5.7
> +Contact: linux-iio@...r.kernel.org
> +Description:
> + Illuminance measuremed in red, green or blue channels, units
> + after application of scale and offset are lux.
No they aren't. Units are some magic intensity at some magic wavelength.
> +
> +What: /sys/.../iio:deviceX/in_illuminance_x_raw
> +What: /sys/.../iio:deviceX/in_illuminance_y_raw
> +What: /sys/.../iio:deviceX/in_illuminance_z_raw
> +KernelVersion: 5.7
> +Contact: linux-iio@...r.kernel.org
> +Description:
> + lluminance measured in the CIE 1931 color space (XYZ).
> + in_illuminance_y_raw is a measure of the brightness, and is
> + identical in_illuminance_raw.
That is fair enough.
> + in_illuminance_x_raw and in_illuminance_z_raw carry chromacity
> + information.
> + in_illuminance_x,y,z_raw are be obtained from the sensor color
> + channels using color matching functions that may be device
> + specific.
> + Units after application of scale and offset are lux.
True for Y, not for X and Z which don't have 'units' as such.
> + The measurments can be used to represent colors in the CIE
> + xyY color space
XYZ
> +
> What: /sys/.../iio:deviceX/in_intensityY_raw
> What: /sys/.../iio:deviceX/in_intensityY_ir_raw
> What: /sys/.../iio:deviceX/in_intensityY_both_raw
Powered by blists - more mailing lists