From: Chang Yu <marcus.yu.56@gmail.com>
To: Joshua Crofts <joshua.crofts1@gmail.com>
Cc: "Chang Yu" <marcus.yu.56@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"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>,
"Shi Hao" <i.shihao.999@gmail.com>,
"Jose A. Perez de Azpillaga" <azpijr@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/2] dt-bindings: iio: light: add as7343
Date: Tue, 13 Oct 2026 23:15:21 +0800 [thread overview]
Message-ID: <as5LCasyTFjTNL0x@zephyrus-g14.localdomain> (raw)
In-Reply-To: <20261013143639.000017b9@gmail.com>
On Tue, Oct 13, 2026 at 02:36:39PM +0200, Joshua Crofts wrote:
> On Tue, 13 Oct 2026 19:56:38 +0800
> Chang Yu <marcus.yu.56@gmail.com> wrote:
>
> > Add binding for AMS AS7343 which is a 14-channel multi-spectral sensor
> > with i2c address of 0x39.
> >
> > The GPIO pin is not described because the datasheet does not document
> > how to use it for hardware synchronization at all. The GPIO register
> > also has no mode-select bit to isolate the pin from the chip's
> > internal control logic. Exposing it as a generic GPIO could result
> > in kernel writes being overwritten by internal logic.
> >
> > Datasheet: https://look.ams-osram.com/m/5f2d27fff9a874d2/original/AS7343-14-Channel-Multi-Spectral-Sensor.pdf
> > Signed-off-by: Chang Yu <marcus.yu.56@gmail.com>
> > ---
> > Changes in v6:
> > - Add a ref to leds/common.yaml for the LDR pin.
> >
> > Changes in v5:
> > - Remove the GPIO pin.
> >
> > Changes in v4:
> > - Fix led-max-microamp property name.
> >
> > Changes in v3:
> > - Add missing include for gpio.
> > - Expand GPIO descrption to include hardware synchronization.
> > - Use led-max-microamp instead of led-current-microamp for the LDR pin.
> >
> > Changes in v2:
> > - Add the LDR, the interrupt pin, and the GPIO pin to the bindings.
> > - Fix node name and unit address mismatch.
> > - Include MAINTAINERS changes.
> >
> > .../bindings/iio/light/ams,as7343.yaml | 66 +++++++++++++++++++
> > MAINTAINERS | 6 ++
> > 2 files changed, 72 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/iio/light/ams,as7343.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/iio/light/ams,as7343.yaml b/Documentation/devicetree/bindings/iio/light/ams,as7343.yaml
> > new file mode 100644
> > index 000000000000..7fb10b0d4843
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/light/ams,as7343.yaml
> > @@ -0,0 +1,66 @@
> > +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/iio/light/ams,as7343.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: AMS AS7343 14-Channel Multi-Spectral Sensor
> > +
> > +maintainers:
> > + - Chang Yu <marcus.yu.56@gmail.com>
> > +
> > +description: |
> > + The AMS AS7343 is a 14-channel multi-spectral sensor with i2c address of 0x39.
> > + https://look.ams-osram.com/m/5f2d27fff9a874d2/original/AS7343-14-Channel-Multi-Spectral-Sensor.pdf
> > +
> > +properties:
> > + compatible:
> > + enum:
> > + - ams,as7343
> > +
> > + reg:
> > + description:
> > + I2C address of the device (0x39).
> > + maxItems: 1
> > +
> > + interrupts:
> > + description:
> > + Open drain output active low interrupt pin.
> > + maxItems: 1
> > +
> > + vdd-supply: true
> > +
> > + led-max-microamp:
> > + description:
> > + The driver current for the external LED connected to the LDR pin.
> > + minimum: 4000
> > + maximum: 258000
> > + multipleOf: 2000
> > + default: 12000
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - vdd-supply
> > +
> > +additionalProperties: false
>
> Should be unevaluatedProperties as you're using $refs in the binding,
> but Jonathan could tweak that when applying.
>
There was a discussion about this back in v2 in which Conor was suggesting
keeping additionalProperties: false if I recall. I don't know the exact
pros vs cons so I'll defer to the experts here.
next prev parent reply other threads:[~2026-10-13 15:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 11:56 [PATCH v6 0/2] Add support for AS7343 multi-spectral sensor Chang Yu
2026-10-13 11:56 ` [PATCH v6 1/2] dt-bindings: iio: light: add as7343 Chang Yu
2026-10-13 12:36 ` Joshua Crofts
2026-10-13 15:15 ` Chang Yu [this message]
2026-10-15 7:41 ` Joshua Crofts
2026-10-13 21:23 ` Jose A. Perez de Azpillaga
2026-10-14 11:22 ` Krzysztof Kozlowski
2026-10-13 11:56 ` [PATCH v6 2/2] iio: light: add AS7343 multi-spectral sensor driver Chang Yu
2026-10-13 12:35 ` Joshua Crofts
2026-10-13 16:28 ` Andy Shevchenko
2026-10-13 16:27 ` Andy Shevchenko
2026-10-14 3:17 ` Chang Yu
2026-10-14 10:38 ` Andy Shevchenko
2026-10-14 10:04 ` Jose A. Perez de Azpillaga
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=as5LCasyTFjTNL0x@zephyrus-g14.localdomain \
--to=marcus.yu.56@gmail.com \
--cc=andy@kernel.org \
--cc=azpijr@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=i.shihao.999@gmail.com \
--cc=jic23@kernel.org \
--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
all inboxes | Powered by JetHome®