From: sashiko-bot@kernel.org
To: "Esben Haabendal" <esben@geanix.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: iio: light: ltr501: Add ltr329 compatible
Date: Wed, 15 Jul 2026 08:27:52 +0000 [thread overview]
Message-ID: <20260715082753.09E7A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260715-liteon-ltr329-v1-2-31f027051594@geanix.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The schema fails to disallow the `interrupts` property for the `liteon,ltr329` compatible string, despite the device explicitly lacking interrupt support.
--
--- Patch [2]: [PATCH 2/3] dt-bindings: iio: light: ltr501: Add ltr329 compatible ---
commit 5d6bf65302b94ef38e976c911c22a66db543f0fe
Author: Esben Haabendal <esben@geanix.com>
dt-bindings: iio: light: ltr501: Add ltr329 compatible
LTR-329ALS-01 is an ambient light sensor similar to LTR-303ALS-01, but
without interrupt support.
> diff --git a/Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml b/Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml
> index ab9bb68dd7363..76e81eba7ea4a 100644
> --- a/Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml
> +++ b/Documentation/devicetree/bindings/iio/light/liteon,ltr501.yaml
> @@ -19,6 +19,7 @@ properties:
> - liteon,ltr559
> - liteon,ltr301
> - liteon,ltr303
> + - liteon,ltr329
>
> reg:
> maxItems: 1
[Severity: Medium]
Since the commit message states this sensor operates without interrupt support,
should the schema disallow the interrupts property for this compatible string?
Adding the compatible string directly to the main enum allows a device tree to
specify an interrupt for liteon,ltr329 without being caught during schema
validation.
Would it make sense to add an if/then conditional block to restrict the
interrupts property when the compatible string is liteon,ltr329 to prevent
this regression?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260715-liteon-ltr329-v1-0-31f027051594@geanix.com?part=2
next prev parent reply other threads:[~2026-07-15 8:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 8:23 [PATCH 0/3] iio: light: ltr501: Add ltr329 support Esben Haabendal
2026-07-15 8:23 ` [PATCH 1/3] dt-bindings: iio: light: ltr501: Add missing ltr303 compatible Esben Haabendal
2026-07-15 8:23 ` [PATCH 2/3] dt-bindings: iio: light: ltr501: Add ltr329 compatible Esben Haabendal
2026-07-15 8:27 ` sashiko-bot [this message]
2026-07-15 8:23 ` [PATCH 3/3] iio: light: ltr501: Add ltr329 driver support Esben Haabendal
2026-07-15 8:38 ` sashiko-bot
2026-07-15 11:53 ` Esben Haabendal
2026-07-15 9:00 ` Joshua Crofts
2026-07-15 12:25 ` Esben Haabendal
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=20260715082753.09E7A1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=esben@geanix.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.