From: Arthur Becker <arthur.becker@sentec.com>
To: Jonathan Cameron <jic23@kernel.org>, "robh@kernel.org" <robh@kernel.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: [PATCH] dt-bindings: iio: light: add veml6040 RGBW-LS bindings
Date: Mon, 13 May 2024 14:35:44 +0000 [thread overview]
Message-ID: <ZR1P278MB1117B205886E023F9F72A2E881E22@ZR1P278MB1117.CHEP278.PROD.OUTLOOK.COM> (raw)
This commit adds device tree bindings for the veml6040 RGBW Light Sensor
signed-off-by: Arthur Becker <arthur.becker@sentec.com>
---
.../bindings/iio/light/veml6040.yaml | 43 +++++++++++++++++++
1 file changed, 43 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/light/veml6040.yaml
diff --git a/Documentation/devicetree/bindings/iio/light/veml6040.yaml b/Documentation/devicetree/bindings/iio/light/veml6040.yaml
new file mode 100644
index 000000000000..796c22f75575
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/light/veml6040.yaml
@@ -0,0 +1,43 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/light/veml6040.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: VEML6040 RGBW Light Sensor
+
+maintainers:
+ - Arthur Becker <arthur.becker@sentec.com>
+
+description: |
+ Datasheet at https://www.vishay.com/docs/84276/veml6040.pdf
+
+properties:
+ compatible:
+ enum:
+ - vishay,veml6040
+
+ reg:
+ description:
+ I2C address of the device.
+ enum:
+ - 0x10
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ light-sensor@10 {
+ compatible = "vishay,veml6040";
+ reg = <0x10>;
+ };
+ };
+...
--
2.34.1
next reply other threads:[~2024-05-13 14:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 14:35 Arthur Becker [this message]
2024-05-13 16:26 ` [PATCH] dt-bindings: iio: light: add veml6040 RGBW-LS bindings Conor Dooley
2024-05-19 11:57 ` Jonathan Cameron
2024-05-19 12:02 ` Conor Dooley
2024-05-19 12:25 ` Jonathan Cameron
2024-05-14 7:10 ` Krzysztof Kozlowski
2024-05-14 7:11 ` Krzysztof Kozlowski
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=ZR1P278MB1117B205886E023F9F72A2E881E22@ZR1P278MB1117.CHEP278.PROD.OUTLOOK.COM \
--to=arthur.becker@sentec.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).