From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] iio: light: veml3328: add devicetree binding for new sensor
Date: Sun, 17 May 2026 14:10:54 +0100 [thread overview]
Message-ID: <20260517141054.3981672c@jic23-huawei> (raw)
In-Reply-To: <20260516-veml3328-v1-1-1d4b663e2fe3@gmail.com>
On Sat, 16 May 2026 23:50:53 +0200
Joshua Crofts <joshua.crofts1@gmail.com> wrote:
> Add devicetree binding for the Vishay VEML3328 RGB/IR light sensor
> connected via I2C (SMBus compatible).
>
> Additionally, add an entry in MAINTAINERS.
>
> Signed-off-by: Joshua Crofts <joshua.crofts1@gmail.com>
This is very standard looking. Have you considered if any similar
bindings can be easily extended to cover this device?
Note that there is no direct relationship between bindings and
drivers, there are single bindings with multiple associated drivers
and multiple bindings covered by a single driver.
Also dt-bindings get used in multiple projects and some of those
will do different splits in what code covers what parts.
Jonathan
next prev parent reply other threads:[~2026-05-17 13:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 21:50 [PATCH 0/2] iio: light: veml3328: add support for new sensor Joshua Crofts
2026-05-16 21:50 ` [PATCH 1/2] iio: light: veml3328: add devicetree binding " Joshua Crofts
2026-05-17 8:38 ` Krzysztof Kozlowski
2026-05-17 10:38 ` Joshua Crofts
2026-05-17 13:08 ` Jonathan Cameron
2026-05-17 13:10 ` Jonathan Cameron [this message]
2026-05-17 14:26 ` Joshua Crofts
2026-05-18 14:18 ` Joshua Crofts
2026-05-18 15:26 ` Jonathan Cameron
2026-05-16 21:50 ` [PATCH 2/2] iio: light: veml3328: add support for new device Joshua Crofts
2026-05-16 22:18 ` sashiko-bot
2026-05-16 22:30 ` Joshua Crofts
2026-05-17 7:53 ` Andy Shevchenko
2026-05-17 11:39 ` Joshua Crofts
2026-05-17 13:34 ` Jonathan Cameron
2026-05-17 14:21 ` Joshua Crofts
2026-05-17 15:55 ` Jonathan Cameron
2026-05-17 17:11 ` Joshua Crofts
2026-05-18 6:44 ` Andy Shevchenko
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=20260517141054.3981672c@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=joshua.crofts1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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