From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
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>,
Rishi Gupta <gupt21@gmail.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: [PATCH v3 3/9] dt-bindings: iio: light: veml6030: add vdd-supply property
Date: Tue, 01 Oct 2024 22:21:16 +0200 [thread overview]
Message-ID: <20241001-veml6035-v3-3-d789f6ff147c@gmail.com> (raw)
In-Reply-To: <20241001-veml6035-v3-0-d789f6ff147c@gmail.com>
Add vdd-supply to account for the sensor's power source.
Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
---
Documentation/devicetree/bindings/iio/light/vishay,veml6030.yaml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/iio/light/vishay,veml6030.yaml b/Documentation/devicetree/bindings/iio/light/vishay,veml6030.yaml
index 7f4995557570..42a78cd4f812 100644
--- a/Documentation/devicetree/bindings/iio/light/vishay,veml6030.yaml
+++ b/Documentation/devicetree/bindings/iio/light/vishay,veml6030.yaml
@@ -41,9 +41,12 @@ properties:
interrupt client node bindings.
maxItems: 1
+ vdd-supply: true
+
required:
- compatible
- reg
+ - vdd-supply
additionalProperties: false
@@ -59,6 +62,7 @@ examples:
compatible = "vishay,veml6030";
reg = <0x10>;
interrupts = <12 IRQ_TYPE_LEVEL_LOW>;
+ vdd-supply = <&vdd>;
};
};
...
--
2.43.0
next prev parent reply other threads:[~2024-10-01 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 20:21 [PATCH v3 0/9] iio: light: veml6030: fix issues and add support for veml6035 Javier Carrasco
2024-10-01 20:21 ` [PATCH v3 1/9] iio: light: veml6030: add set up delay after any power on sequence Javier Carrasco
2024-10-01 20:21 ` [PATCH v3 2/9] iio: light: veml6030: use dev_err_probe() Javier Carrasco
2024-10-01 20:21 ` Javier Carrasco [this message]
2024-10-01 20:21 ` [PATCH v3 4/9] iio: light: veml6030: add support for a regulator Javier Carrasco
2024-10-01 20:21 ` [PATCH v3 5/9] iio: light: veml6030: use read_avail() for available attributes Javier Carrasco
2024-10-01 20:21 ` [PATCH v3 6/9] iio: light: veml6030: drop processed info for white channel Javier Carrasco
2024-10-01 20:21 ` [PATCH v3 7/9] iio: light: veml6030: power off device in probe error paths Javier Carrasco
2024-10-01 20:21 ` [PATCH v3 8/9] dt-bindings: iio: light: veml6030: add veml6035 Javier Carrasco
2024-10-01 20:21 ` [PATCH v3 9/9] iio: light: veml6030: add support for veml6035 Javier Carrasco
2024-10-06 14:10 ` [PATCH v3 0/9] iio: light: veml6030: fix issues and " 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=20241001-veml6035-v3-3-d789f6ff147c@gmail.com \
--to=javier.carrasco.cruz@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gupt21@gmail.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@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;
as well as URLs for NNTP newsgroup(s).