devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mudit Sharma <muditsharma.info@gmail.com>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
	jic23@kernel.org, lars@metafoo.de, krzk+dt@kernel.org,
	conor+dt@kernel.org, robh@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org, Ivan Orlov <ivan.orlov0322@gmail.com>,
	Javier Carrasco <javier.carrasco.cruz@gmail.com>
Subject: Re: [PATCH v8 2/2] iio: light: ROHM BH1745 colour sensor
Date: Tue, 6 Aug 2024 21:45:07 +0100	[thread overview]
Message-ID: <23e8b9d9-d0e0-44df-b464-fc2d1f2d5507@gmail.com> (raw)
In-Reply-To: <5622f011-222a-459e-9086-138adf0796aa@gmail.com>

On 05/08/2024 11:28, Matti Vaittinen wrote:
> On 7/19/24 01:02, Mudit Sharma 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.
>>
>> Interrupt source for the device can be configured by enabling the
>> corresponding event. Interrupt latch is always enabled when setting
>> up interrupt.
>>
>> Add myself as the maintainer for this driver in MAINTAINERS.
>>
>> Signed-off-by: Mudit Sharma <muditsharma.info@gmail.com>
>> Reviewed-by: Ivan Orlov <ivan.orlov0322@gmail.com>
>> Reviewed-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> 
> Hi Mudit & All :)
> 
> I know I am late. The series has already been applied (thanks 
> Jonathan!). I've mostly been offline for the last 1.5 months or so - 
> "all work and no play makes Jack a dull boy", you know ;)
> 
> Anyways, as Jonathan asked me to take a look at the GTS stuff (at v7), I 
> tried to quickly glance at this. It looks good to me!
> 
> Well, the real test will be the users of the sensor driver - so please 
> let us know if GTS stuff brings problems to users. I am mostly 
> interested in knowing if gain changes caused by integration time changes 
> are handled gracefully by the users. :) Well, seeing there is no per- 
> channel gain or integration time setting, you should be safe from the 
> worst side-effects :)
> 
> Nice driver!

Hi Matti,

Thank you for your review on this :)

Best regards,
Mudit Sharma
> 
> Yours,
>      -- Matti
> 


      reply	other threads:[~2024-08-06 20:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18 22:02 [PATCH v8 1/2] dt-bindings: iio: light: ROHM BH1745 Mudit Sharma
2024-07-18 22:02 ` [PATCH v8 2/2] iio: light: ROHM BH1745 colour sensor Mudit Sharma
2024-07-19 16:02   ` Javier Carrasco
2024-07-20 18:29     ` Mudit Sharma
2024-07-20 16:29   ` Jonathan Cameron
2024-07-20 18:25     ` Mudit Sharma
2024-08-05 10:28   ` Matti Vaittinen
2024-08-06 20:45     ` Mudit Sharma [this message]

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=23e8b9d9-d0e0-44df-b464-fc2d1f2d5507@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).