devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mudit Sharma <muditsharma.info@gmail.com>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
	Jonathan Cameron <jic23@kernel.org>
Cc: lars@metafoo.de, krzk+dt@kernel.org, conor+dt@kernel.org,
	robh@kernel.org, ivan.orlov0322@gmail.com,
	javier.carrasco.cruz@gmail.com, linux-kernel@vger.kernel.org,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 2/2] iio: light: ROHM BH1745 colour sensor
Date: Mon, 17 Jun 2024 19:52:55 +0100	[thread overview]
Message-ID: <67dca4c3-bb86-4cd4-b80b-733ba93547b9@gmail.com> (raw)
In-Reply-To: <CANhJrGM9czj0RL3OLCgRHEKc2QOjG9P0AZTrZxvYUk65TCpHRg@mail.gmail.com>

On 10/06/2024 06:58, Matti Vaittinen wrote:
> la 8. kesäk. 2024 klo 19.22 Jonathan Cameron (jic23@kernel.org) kirjoitti:
>>
>> On Thu,  6 Jun 2024 17:29:42 +0100
>> Mudit Sharma <muditsharma.info@gmail.com> wrote:
>>
>>> Add support for BH1745, which is an I2C colour sensor with red, green,
>>> blue and clear channels. It has a programmable active low interrupt
>>> pin. Interrupt occurs when the signal from the selected interrupt
>>> source channel crosses set interrupt threshold high or low level.
>>>
>>> This driver includes device attributes to configure the following:
>>> - Interrupt pin latch: The interrupt pin can be configured to
>>>    be latched (until interrupt register (0x60) is read or initialized)
>>>    or update after each measurement.
>>> - Interrupt source: The colour channel that will cause the interrupt
>>>    when channel will cross the set threshold high or low level.
>>>
>>> This driver also includes device attributes to present valid
>>> configuration options/values for:
>>> - Integration time
>>> - Interrupt colour source
>>> - Hardware gain
>>>
> 
>>> +
>>> +#define BH1745_CHANNEL(_colour, _si, _addr)                                   \
>>> +     {                                                                     \
>>> +             .type = IIO_INTENSITY, .modified = 1,                         \
>>> +             .info_mask_separate = BIT(IIO_CHAN_INFO_RAW),                 \
>>> +             .info_mask_shared_by_type = BIT(IIO_CHAN_INFO_HARDWAREGAIN) | \
>>
>> Provide _SCALE instead of HARDWAREGAIN
>> As it's an intensity channel (and units are tricky for color sensors given
>> frequency dependence etc) all you need to do is ensure that if you halve
>> the _scale and measure the same light source, the computed
>> _RAW * _SCALE value remains constant.
> 
> ...Which is likely to cause also the integration time setting to
> impact the SCALE.
> 
> You may or may not want to see the GTS-helpers
> (drivers/iio/industrialio-gts-helper.c) - which have their own tricky
> corners. I think Jonathan once suggested to me to keep the

Hi Matti,

Thank you for the recommendation here.

Looking into GTS-helper for v5.

Best regards,
Mudit Sharma

  parent reply	other threads:[~2024-06-17 18:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-06 16:29 [PATCH v4 1/2] dt-bindings: iio: light: ROHM BH1745 Mudit Sharma
2024-06-06 16:29 ` [PATCH v4 2/2] iio: light: ROHM BH1745 colour sensor Mudit Sharma
2024-06-08 16:22   ` Jonathan Cameron
2024-06-10  5:58     ` Matti Vaittinen
2024-06-11 17:14       ` Jonathan Cameron
2024-06-12  6:07         ` Matti Vaittinen
2024-06-15 18:23           ` Jonathan Cameron
2024-06-17  7:08             ` Matti Vaittinen
2024-06-23 16:52               ` Jonathan Cameron
2024-06-17 18:52       ` Mudit Sharma [this message]
2024-06-17 18:47     ` Mudit Sharma
2024-06-08 15:27 ` [PATCH v4 1/2] dt-bindings: iio: light: ROHM BH1745 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=67dca4c3-bb86-4cd4-b80b-733ba93547b9@gmail.com \
    --to=muditsharma.info@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=ivan.orlov0322@gmail.com \
    --cc=javier.carrasco.cruz@gmail.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mazziesaccount@gmail.com \
    --cc=robh@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).