From: sashiko-bot@kernel.org
To: "Jad Keskes" <inasj268@gmail.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4] dt-bindings: misc: convert lis302.txt to YAML
Date: Fri, 19 Jun 2026 12:53:30 +0000 [thread overview]
Message-ID: <20260619125331.1F3501F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260619124426.882626-1-inasj268@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The YAML binding erroneously forbids `Vdd-supply` and `Vdd_IO-supply` for the SPI variant by setting them to `false`.
--
commit 286d4c20f34dbb3740102063ad8a21275e5828b2
Author: Jad Keskes <inasj268@gmail.com>
dt-bindings: misc: convert lis302.txt to YAML
This commit converts the old LIS302 accelerometer plain text binding into a
YAML schema. It covers both I2C and SPI variants and retains deprecated
property names for backwards compatibility.
> diff --git a/Documentation/devicetree/bindings/misc/st,lis3lv02d.yaml b/Documentation/devicetree/bindings/misc/st,lis3lv02d.yaml
> new file mode 100644
> index 0000000000000..c73371b754a1e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/misc/st,lis3lv02d.yaml
[ ... ]
> +allOf:
> + - if:
> + properties:
> + compatible:
> + not:
> + contains:
> + const: st,lis302dl-spi
> + then:
> + required:
> + - Vdd-supply
> + - Vdd_IO-supply
> + else:
> + properties:
> + Vdd-supply: false
> + Vdd_IO-supply: false
[Severity: Medium]
Does forbidding these power supplies for the SPI variant prevent accurate
hardware description?
The hardware physically requires Vdd and Vdd_IO power supplies to function,
regardless of whether it is accessed via I2C or SPI. Setting these
properties to false in the else branch explicitly forbids device tree
writers from modeling the physical regulators powering the SPI device,
which will cause valid hardware descriptions to fail dtbs_check schema
validation.
> + required:
> + - spi-max-frequency
> + - interrupts
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260619124426.882626-1-inasj268@gmail.com?part=1
prev parent reply other threads:[~2026-06-19 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 11:56 [PATCH 1/2] dt-bindings: misc: convert lis302.txt to YAML Jad Keskes
2026-06-19 11:56 ` [PATCH 2/2] dt-bindings: iio: st-sensors: drop lis302dl-spi from deprecated list Jad Keskes
2026-06-19 12:06 ` sashiko-bot
2026-06-19 12:09 ` [PATCH 1/2] dt-bindings: misc: convert lis302.txt to YAML sashiko-bot
2026-06-19 12:24 ` [PATCH v3] " Jad Keskes
2026-06-19 12:39 ` sashiko-bot
2026-06-19 12:44 ` [PATCH v4] " Jad Keskes
2026-06-19 12:53 ` sashiko-bot [this message]
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=20260619125331.1F3501F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inasj268@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.