linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Parthiban Nallathambi <pn@denx.de>
To: Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Cc: pn@denx.de, jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
	robh+dt@kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, mark.rutland@arm.com,
	devicetree@vger.kernel.org, matthias.bgg@gmail.com, wd@denx.de,
	sbabic@denx.de, hs@denx.de
Subject: Re: [PATCH v4 1/3] iio: Add modifier for white light
Date: Fri, 3 Aug 2018 12:44:44 +0200	[thread overview]
Message-ID: <fb30878f-0163-306a-e933-d9fecc996acb@denx.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1808022117460.25216@vps.pmeerw.net>

Hello Peter,

On 08/02/2018 09:30 PM, Peter Meerwald-Stadler wrote:
> Hello,
> 
> it is not clear to me why 'white' is needed;
> isn't that the default, i.e. unfiltered light?

Yes, it is. But devices like vcnl4035 veml7700, White LED data one
register and all other sources of light (like fluorescent,
incandescent ,sunlight) in separate register.

So in such cases this WHITE modifier is needed. Should it needs to
come under IIO_MOD_LIGHT_CLEAR?

> 
> thanks, regards, p.
> 
>> Signed-off-by: Parthiban Nallathambi <pn@denx.de>
>> ---
>>   Documentation/ABI/testing/sysfs-bus-iio | 7 +++++++
>>   drivers/iio/industrialio-core.c         | 1 +
>>   include/uapi/linux/iio/types.h          | 1 +
>>   tools/iio/iio_event_monitor.c           | 2 ++
>>   4 files changed, 11 insertions(+)
>>
>> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
>> index 731146c3b138..43e481aed5b2 100644
>> --- a/Documentation/ABI/testing/sysfs-bus-iio
>> +++ b/Documentation/ABI/testing/sysfs-bus-iio
>> @@ -1312,6 +1312,13 @@ Description:
>>   		standardised CIE Erythemal Action Spectrum. UV index values range
>>   		from 0 (low) to >=11 (extreme).
>>   
>> +What:		/sys/.../iio:deviceX/in_intensityY_white_raw
>> +KernelVersion:	4.18
>> +Contact:	linux-iio@vger.kernel.org
>> +Description:
>> +		Modifier white indicates that measurements contain white LED
>> +		component.
>> +
>>   What:		/sys/.../iio:deviceX/in_intensity_red_integration_time
>>   What:		/sys/.../iio:deviceX/in_intensity_green_integration_time
>>   What:		/sys/.../iio:deviceX/in_intensity_blue_integration_time
>> diff --git a/drivers/iio/industrialio-core.c b/drivers/iio/industrialio-core.c
>> index 19bdf3d2962a..cb939b9fad16 100644
>> --- a/drivers/iio/industrialio-core.c
>> +++ b/drivers/iio/industrialio-core.c
>> @@ -108,6 +108,7 @@ static const char * const iio_modifier_names[] = {
>>   	[IIO_MOD_LIGHT_GREEN] = "green",
>>   	[IIO_MOD_LIGHT_BLUE] = "blue",
>>   	[IIO_MOD_LIGHT_UV] = "uv",
>> +	[IIO_MOD_LIGHT_WHITE] = "white",
>>   	[IIO_MOD_QUATERNION] = "quaternion",
>>   	[IIO_MOD_TEMP_AMBIENT] = "ambient",
>>   	[IIO_MOD_TEMP_OBJECT] = "object",
>> diff --git a/include/uapi/linux/iio/types.h b/include/uapi/linux/iio/types.h
>> index 4213cdf88e3c..de87a6c7e6de 100644
>> --- a/include/uapi/linux/iio/types.h
>> +++ b/include/uapi/linux/iio/types.h
>> @@ -84,6 +84,7 @@ enum iio_modifier {
>>   	IIO_MOD_CO2,
>>   	IIO_MOD_VOC,
>>   	IIO_MOD_LIGHT_UV,
>> +	IIO_MOD_LIGHT_WHITE,
>>   };
>>   
>>   enum iio_event_type {
>> diff --git a/tools/iio/iio_event_monitor.c b/tools/iio/iio_event_monitor.c
>> index b61245e1181d..a2f9c62a79dd 100644
>> --- a/tools/iio/iio_event_monitor.c
>> +++ b/tools/iio/iio_event_monitor.c
>> @@ -96,6 +96,7 @@ static const char * const iio_modifier_names[] = {
>>   	[IIO_MOD_LIGHT_GREEN] = "green",
>>   	[IIO_MOD_LIGHT_BLUE] = "blue",
>>   	[IIO_MOD_LIGHT_UV] = "uv",
>> +	[IIO_MOD_LIGHT_WHITE] = "white",
>>   	[IIO_MOD_QUATERNION] = "quaternion",
>>   	[IIO_MOD_TEMP_AMBIENT] = "ambient",
>>   	[IIO_MOD_TEMP_OBJECT] = "object",
>> @@ -178,6 +179,7 @@ static bool event_is_known(struct iio_event_data *event)
>>   	case IIO_MOD_LIGHT_GREEN:
>>   	case IIO_MOD_LIGHT_BLUE:
>>   	case IIO_MOD_LIGHT_UV:
>> +	case IIO_MOD_LIGHT_WHITE:
>>   	case IIO_MOD_QUATERNION:
>>   	case IIO_MOD_TEMP_AMBIENT:
>>   	case IIO_MOD_TEMP_OBJECT:
>>
> 

-- 
Thanks,
Parthiban Nallathambi

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de

  reply	other threads:[~2018-08-03 10:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02 18:27 [PATCH v4 1/3] iio: Add modifier for white light Parthiban Nallathambi
2018-08-02 18:27 ` [PATCH v4 2/3] iio: light: Add support for vishay vcnl4035 Parthiban Nallathambi
2018-08-02 19:29   ` Peter Meerwald-Stadler
2018-08-02 19:34   ` Andy Shevchenko
2018-08-03 20:55     ` Jonathan Cameron
2018-08-02 18:27 ` [PATCH v4 3/3] iio: light: Add device tree binding " Parthiban Nallathambi
2018-08-02 19:30 ` [PATCH v4 1/3] iio: Add modifier for white light Peter Meerwald-Stadler
2018-08-03 10:44   ` Parthiban Nallathambi [this message]
2018-08-03 11:38     ` Peter Meerwald-Stadler
2018-08-03 20:34       ` 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=fb30878f-0163-306a-e933-d9fecc996acb@denx.de \
    --to=pn@denx.de \
    --cc=devicetree@vger.kernel.org \
    --cc=hs@denx.de \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    --cc=sbabic@denx.de \
    --cc=wd@denx.de \
    /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).