From: Arthur Becker via B4 Relay <devnull+arthur.becker.sentec.com@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org,
Arthur Becker <arthur.becker@sentec.com>
Subject: [PATCH v3 2/2] dt-bindings: iio: light: add VEML6040 RGBW-LS bindings
Date: Mon, 27 May 2024 17:12:09 +0200 [thread overview]
Message-ID: <20240527-veml6040-v3-2-6f3bbfd42960@sentec.com> (raw)
In-Reply-To: <20240527-veml6040-v3-0-6f3bbfd42960@sentec.com>
From: Arthur Becker <arthur.becker@sentec.com>
Device tree bindings for the vishay VEML6040 RGBW light sensor iio
driver
Signed-off-by: Arthur Becker <arthur.becker@sentec.com>
---
V1 -> V3: Addressed review comments (v1 of the dt-bindings was sent
along with v2 of the driver but not in a set)
---
.../bindings/iio/light/vishay,veml6040.yaml | 44 ++++++++++++++++++++++
1 file changed, 44 insertions(+)
diff --git a/Documentation/devicetree/bindings/iio/light/vishay,veml6040.yaml b/Documentation/devicetree/bindings/iio/light/vishay,veml6040.yaml
new file mode 100644
index 000000000000..101c2cc6506e
--- /dev/null
+++ b/Documentation/devicetree/bindings/iio/light/vishay,veml6040.yaml
@@ -0,0 +1,44 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/light/vishay,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:
+ const: vishay,veml6040
+
+ reg:
+ enum:
+ - 0x10
+
+ vdd-supply: true
+
+required:
+ - compatible
+ - reg
+ - vdd-supply
+
+additionalProperties: false
+
+examples:
+ - |
+ i2c {
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ light-sensor@10 {
+ compatible = "vishay,veml6040";
+ reg = <0x10>;
+ vdd-supply = <&vdd_reg>;
+ };
+ };
+...
--
2.34.1
next prev parent reply other threads:[~2024-05-27 15:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 15:12 [PATCH v3 0/2] Add driver for Vishay VEML6040 Arthur Becker via B4 Relay
2024-05-27 15:12 ` [PATCH v3 1/2] iio: light: " Arthur Becker via B4 Relay
2024-06-02 13:22 ` Jonathan Cameron
2024-06-03 12:18 ` Arthur Becker
2024-06-03 18:22 ` Jonathan Cameron
2024-05-27 15:12 ` Arthur Becker via B4 Relay [this message]
2024-05-27 16:30 ` [PATCH v3 2/2] dt-bindings: iio: light: add VEML6040 RGBW-LS bindings Conor Dooley
2024-05-28 7:15 ` [EXTERNAL]Re: " Arthur Becker
2024-05-27 16:31 ` Krzysztof Kozlowski
2024-05-28 7:23 ` [EXTERNAL]Re: " Arthur Becker
2024-05-28 10:05 ` Jonathan Cameron
2024-05-30 9:00 ` Arthur Becker
2024-05-28 14:39 ` Rob Herring
2024-05-30 9:00 ` Arthur Becker
2024-06-02 13:16 ` Jonathan Cameron
2024-06-03 8:23 ` Arthur Becker
2024-06-03 8:25 ` Jonathan Cameron
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=20240527-veml6040-v3-2-6f3bbfd42960@sentec.com \
--to=devnull+arthur.becker.sentec.com@kernel.org \
--cc=arthur.becker@sentec.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--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