From: sashiko-bot@kernel.org
To: "Svyatoslav Ryhel" <clamor95@gmail.com>
Cc: mfd@lists.linux.dev, lee@kernel.org, robh@kernel.org,
dri-devel@lists.freedesktop.org, linux-leds@vger.kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v1 1/3] dt-bindings: mfd: Document Skyworks AAT2870
Date: Wed, 30 Sep 2026 07:25:10 +0000 [thread overview]
Message-ID: <20260930072511.3DB6D1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260930071513.54697-2-clamor95@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] leds: incorrect scaling for led-max-microamp constraints
--
commit 629a67ba3ff0e9f6e02a0fa733445881d67a7d0c
Author: Svyatoslav Ryhel <clamor95@gmail.com>
dt-bindings: mfd: Document Skyworks AAT2870
Document Skyworks AAT2870 LED Backlight Driver and Multiple LDO Lighting
Management Unit.
> diff --git a/Documentation/devicetree/bindings/leds/skyworks,aat2870.yaml b/Documentation/devicetree/bindings/leds/skyworks,aat2870.yaml
> new file mode 100644
> index 0000000000000..6dfcd1fa399ca
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/leds/skyworks,aat2870.yaml
> @@ -0,0 +1,127 @@
[ ... ]
> + backlight:
> + $ref: /schemas/leds/backlight/common.yaml#
> + unevaluatedProperties: false
> +
> + properties:
> + compatible:
> + const: skyworks,aat2870-backlight
> +
> + led-max-microamp:
> + minimum: 450000
> + maximum: 27900000
> + default: 450000
[Severity: Medium]
Are these constraints for led-max-microamp mathematically correct? The values
range from 450,000 to 27,900,000 uA, which corresponds to 450 mA to 27.9 Amps.
Real hardware limits appear to be 0.45 mA to 27.9 mA, which would be 450 to
27,900 uA. Defining a physically correct value (e.g., <27900>) in a device
tree will fail schema validation.
> +
> + max-brightness:
> + default: 255
[ ... ]
> + backlight {
> + compatible = "skyworks,aat2870-backlight";
> +
> + skyworks,channels = /bits/ 8 <0xff>;
> + led-max-microamp = <27900000>;
[Severity: Medium]
Does this example propagate the erroneous 27.9 Amps value?
The follow-up driver patch (commit mfd: aat2870: Convert to use OF bindings)
propagates this incorrect scaling, meaning correct values will be wrongly
clamped to minimum brightness.
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930071513.54697-1-clamor95@gmail.com?part=1
next prev parent reply other threads:[~2026-09-30 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 7:15 [PATCH v1 0/3] mfd: aat2870: Convert to use OF bindings Svyatoslav Ryhel
2026-09-30 7:15 ` [PATCH v1 1/3] dt-bindings: mfd: Document Skyworks AAT2870 Svyatoslav Ryhel
2026-09-30 7:25 ` sashiko-bot [this message]
2026-09-30 7:15 ` [PATCH v1 2/3] mfd: aat2870: Convert to use OF bindings Svyatoslav Ryhel
2026-09-30 7:28 ` sashiko-bot
2026-09-30 7:15 ` [PATCH v1 3/3] mfd: aat2870: Add support for VIN and IN-LDO power supplies Svyatoslav Ryhel
2026-09-30 7:24 ` sashiko-bot
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=20260930072511.3DB6D1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=clamor95@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox