Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jad Keskes" <inasj268@gmail.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: iio: st-sensors: drop lis302dl-spi from deprecated list
Date: Fri, 19 Jun 2026 12:06:11 +0000	[thread overview]
Message-ID: <20260619120611.9F3861F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260619115649.840676-2-inasj268@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incorrect Schema Removal / Broken Validation for st,lis302dl-spi
--

commit 23c740836661eab02e0a98566f673ed373f8b4d3
Author: Jad Keskes <inasj268@gmail.com>

dt-bindings: iio: st-sensors: drop lis302dl-spi from deprecated list

This commit removes the st,lis302dl-spi compatible string from the deprecated
list in the IIO st-sensors binding. It claims the compatible string is only
used by the misc driver.

> st,lis302dl-spi is only used by the misc/lis3lv02d driver. Its
> binding is now in Documentation/devicetree/bindings/misc/.

[Severity: Medium]
Is this statement accurate? Looking at drivers/iio/accel/st_accel_spi.c, the
IIO SPI driver still explicitly matches st,lis302dl-spi:

drivers/iio/accel/st_accel_spi.c:st_accel_of_match[] = {
	{
		/* An older compatible */
		.compatible = "st,lis302dl-spi",
		.data = LIS3LV02DL_ACCEL_DEV_NAME,
	},

> diff --git a/Documentation/devicetree/bindings/iio/st,st-sensors.yaml b/Documentation/devicetree/bindings/iio/st,st-sensors.yaml
> index a1a958215cdb7..2a5451589fabf 100644
> --- a/Documentation/devicetree/bindings/iio/st,st-sensors.yaml
> +++ b/Documentation/devicetree/bindings/iio/st,st-sensors.yaml
> @@ -90,10 +90,8 @@ properties:
>            - st,lsm9ds0-imu
>        - description: Deprecated bindings
>          enum:
> -          - st,lis302dl-spi

[Severity: Medium]
If st,lis302dl-spi is removed from the IIO binding, won't dtbs_check fail for
any valid device tree that pairs this compatible string with standard IIO
properties (such as vdd-supply or mount-matrix)?

Since the misc binding (st,lis3lv02d.yaml) enforces additionalProperties: false,
it would reject these IIO properties. It appears st,lis3lv02d was kept in the
schema for the exact same reason that st,lis302dl-spi should be kept.

>            - st,lis3lv02d
>          deprecated: true
> -
>    reg:
>      maxItems: 1

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260619115649.840676-1-inasj268@gmail.com?part=2

  reply	other threads:[~2026-06-19 12:06 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 [this message]
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

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=20260619120611.9F3861F000E9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox