From: Kaustabh Chakraborty <kauschluss@disroot.org>
To: linux-iio@vger.kernel.org, jic23@kernel.org
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
Kaustabh Chakraborty <kauschluss@disroot.org>
Subject: [PATCH 3/3] dt-bindings: iio: light: stk33xx: add compatible for stk3013
Date: Fri, 12 Jul 2024 20:54:02 +0530 [thread overview]
Message-ID: <20240712152417.97726-3-kauschluss@disroot.org> (raw)
In-Reply-To: <20240712152417.97726-1-kauschluss@disroot.org>
Add the compatible string of stk3013 to the existing list.
Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
---
Documentation/devicetree/bindings/iio/light/stk33xx.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/iio/light/stk33xx.yaml b/Documentation/devicetree/bindings/iio/light/stk33xx.yaml
index f6e22dc9814a..6003da66a7e6 100644
--- a/Documentation/devicetree/bindings/iio/light/stk33xx.yaml
+++ b/Documentation/devicetree/bindings/iio/light/stk33xx.yaml
@@ -19,6 +19,7 @@ allOf:
properties:
compatible:
enum:
+ - sensortek,stk3013
- sensortek,stk3310
- sensortek,stk3311
- sensortek,stk3335
--
2.45.2
next prev parent reply other threads:[~2024-07-12 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 15:24 [PATCH 1/3] iio: light: stk3310: relax chipid check warning Kaustabh Chakraborty
2024-07-12 15:24 ` [PATCH 2/3] iio: light: stk3310: add support for stk3013 Kaustabh Chakraborty
2024-07-12 15:24 ` Kaustabh Chakraborty [this message]
2024-07-13 12:06 ` [PATCH 3/3] dt-bindings: iio: light: stk33xx: add compatible " Jonathan Cameron
2024-07-15 20:02 ` Kaustabh Chakraborty
2024-07-16 16:43 ` Jonathan Cameron
2024-07-17 15:58 ` Kaustabh Chakraborty
2024-07-20 12:45 ` Jonathan Cameron
2024-07-13 12:06 ` [PATCH 1/3] iio: light: stk3310: relax chipid check warning Jonathan Cameron
2024-07-14 8:51 ` Kaustabh Chakraborty
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=20240712152417.97726-3-kauschluss@disroot.org \
--to=kauschluss@disroot.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.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;
as well as URLs for NNTP newsgroup(s).