All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Chang Yu" <marcus.yu.56@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: light: add as7343
Date: Thu, 10 Sep 2026 06:49:29 +0000	[thread overview]
Message-ID: <20260910064929.F09671F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260910063813.56419-2-marcus.yu.56@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The generic LED property `led-max-microamp` was incorrectly added with a vendor prefix (`ams,led-max-microamp`), contradicting the commit message and standard property conventions.
--

commit bc94ab43a595b8c728d510d6725b14dbeb5f151f
Author: Chang Yu <marcus.yu.56@gmail.com>

dt-bindings: iio: light: add as7343

Add binding for AMS AS7343 which is a 14-channel multi-spectral sensor
with i2c address of 0x39.

> 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 0000000000000..6b8a05be00430
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/light/ams,as7343.yaml
[ ... ]
> +  vdd-supply: true
> +
> +  ams,led-max-microamp:

[Severity: Medium]
Should this property be defined without the vendor prefix?

The generic LED property led-max-microamp is added here with a vendor
prefix (ams,led-max-microamp), which contradicts standard property
conventions and the stated intent in the patch version changelog.

Device trees written for this device will use this vendor-prefixed
property, creating permanent ABI baggage. If a driver later implements
this feature and correctly parses the standard led-max-microamp, it will
break compatibility with these early device trees or force the driver to
parse both properties.

> +    description:
> +      The driver current for the external LED connected to the LDR pin.
> +    minimum: 4000
> +    maximum: 258000
> +    multipleOf: 2000
> +    default: 12000
> +
[ ... ]
> +        multispectral-sensor@39 {
> +            compatible = "ams,as7343";
> +            reg = <0x39>;
> +            interrupts = <7 IRQ_TYPE_LEVEL_LOW>;
> +            vdd-supply = <&vdd_regulator>;
> +            ams,led-max-microamp = <14000>;

[Severity: Medium]
Would it be better to also remove the vendor prefix from this property in the
device tree example?

> +            sync-gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
> +        };
> +    };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260910063813.56419-1-marcus.yu.56@gmail.com?part=1

  reply	other threads:[~2026-09-10  6:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10  6:38 [PATCH v3 0/2] Add support for AS7343 multi-spectral sensor Chang Yu
2026-09-10  6:38 ` [PATCH v3 1/2] dt-bindings: iio: light: add as7343 Chang Yu
2026-09-10  6:49   ` sashiko-bot [this message]
2026-09-11  8:40   ` Krzysztof Kozlowski
2026-09-10  6:38 ` [PATCH v3 2/2] iio: light: add AS7343 multi-spectral sensor driver Chang Yu
2026-09-10  6:59   ` sashiko-bot
2026-09-10  9:07   ` Andy Shevchenko
2026-09-10 19:22     ` Chang Yu
2026-09-11  5:48       ` 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=20260910064929.F09671F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=marcus.yu.56@gmail.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.