From: Jad Keskes <inasj268@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
Eric Piel <eric.piel@tremplin-utc.net>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Jad Keskes <inasj268@gmail.com>
Subject: [PATCH 2/2] dt-bindings: iio: st-sensors: drop lis302dl-spi from deprecated list
Date: Fri, 19 Jun 2026 12:56:49 +0100 [thread overview]
Message-ID: <20260619115649.840676-2-inasj268@gmail.com> (raw)
In-Reply-To: <20260619115649.840676-1-inasj268@gmail.com>
st,lis302dl-spi is only used by the misc/lis3lv02d driver. Its
binding is now in Documentation/devicetree/bindings/misc/.
Keep st,lis3lv02d in the deprecated list — the IIO i2c driver
still matches it for LIS3LV02DL support.
Tested: dt_binding_check, dtbs_check.
Signed-off-by: Jad Keskes <inasj268@gmail.com>
---
Documentation/devicetree/bindings/iio/st,st-sensors.yaml | 2 --
1 file changed, 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/st,st-sensors.yaml b/Documentation/devicetree/bindings/iio/st,st-sensors.yaml
index a1a958215cdb..2a5451589fab 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
- st,lis3lv02d
deprecated: true
-
reg:
maxItems: 1
--
2.54.0
next prev parent reply other threads:[~2026-06-19 11:57 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 ` Jad Keskes [this message]
2026-06-19 12:06 ` [PATCH 2/2] dt-bindings: iio: st-sensors: drop lis302dl-spi from deprecated list 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
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=20260619115649.840676-2-inasj268@gmail.com \
--to=inasj268@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=eric.piel@tremplin-utc.net \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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