From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Arthur Becker <arthur.becker@sentec.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [EXTERNAL]Re: [PATCH v3 2/2] dt-bindings: iio: light: add VEML6040 RGBW-LS bindings
Date: Tue, 28 May 2024 11:05:11 +0100 [thread overview]
Message-ID: <20240528110511.00006fe5@Huawei.com> (raw)
In-Reply-To: <ZR1P278MB111779FE0C84DB465C54EEFF81F12@ZR1P278MB1117.CHEP278.PROD.OUTLOOK.COM>
On Tue, 28 May 2024 07:23:03 +0000
Arthur Becker <arthur.becker@sentec.com> wrote:
> Thanks for the Review!
> Right, I wasn't sure if and how to add the veml6040 to the veml6075 dt-binding file.
> I'll modify that the next time I make adjustments to the driver.
It's absolutely fine to have shared bindings even if the
drivers (because of different register interface etc) are completely
separate. It's a good way to keep bindings aligned between
similar devices.
Jonathan
>
> Kind regards,
> Arthur
>
> ________________________________________
> From: Krzysztof Kozlowski <krzk@kernel.org>
> Sent: 27 May 2024 18:31
> To: Arthur Becker; Jonathan Cameron; Lars-Peter Clausen; Rob Herring; Krzysztof Kozlowski; Conor Dooley
> Cc: linux-kernel@vger.kernel.org; linux-iio@vger.kernel.org; devicetree@vger.kernel.org
> Subject: [EXTERNAL]Re: [PATCH v3 2/2] dt-bindings: iio: light: add VEML6040 RGBW-LS bindings
>
> On 27/05/2024 17:12, Arthur Becker via B4 Relay wrote:
> > From: Arthur Becker <arthur.becker@sentec.com>
> >
> > Device tree bindings for the vishay VEML6040 RGBW light sensor iio
> > driver
> >
> > Signed-off-by: Arthur Becker <arthur.becker@sentec.com>
> > ---
> > V1 -> V3: Addressed review comments (v1 of the dt-bindings was sent
> > along with v2 of the driver but not in a set)
>
> It's basically the same as veml6075, so should be put there...
>
> Eh,
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> Best regards,
> Krzysztof
>
>
next prev parent reply other threads:[~2024-05-28 10:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 15:12 [PATCH v3 0/2] Add driver for Vishay VEML6040 Arthur Becker via B4 Relay
2024-05-27 15:12 ` [PATCH v3 1/2] iio: light: " Arthur Becker via B4 Relay
2024-06-02 13:22 ` Jonathan Cameron
2024-06-03 12:18 ` Arthur Becker
2024-06-03 18:22 ` Jonathan Cameron
2024-05-27 15:12 ` [PATCH v3 2/2] dt-bindings: iio: light: add VEML6040 RGBW-LS bindings Arthur Becker via B4 Relay
2024-05-27 16:30 ` Conor Dooley
2024-05-28 7:15 ` [EXTERNAL]Re: " Arthur Becker
2024-05-27 16:31 ` Krzysztof Kozlowski
2024-05-28 7:23 ` [EXTERNAL]Re: " Arthur Becker
2024-05-28 10:05 ` Jonathan Cameron [this message]
2024-05-30 9:00 ` Arthur Becker
2024-05-28 14:39 ` Rob Herring
2024-05-30 9:00 ` Arthur Becker
2024-06-02 13:16 ` Jonathan Cameron
2024-06-03 8:23 ` Arthur Becker
2024-06-03 8:25 ` 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=20240528110511.00006fe5@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=arthur.becker@sentec.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).