From: Alisa-Dariana Roman <alisadariana@gmail.com>
To: Alisa-Dariana Roman <alisa.roman@analog.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Michael Hennerich <michael.hennerich@analog.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Alexandru Tachici <alexandru.tachici@analog.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>,
Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Subject: [PATCH v4 4/5] dt-bindings: iio: adc: ad7192: Add clock provider
Date: Thu, 13 Jun 2024 14:40:00 +0300 [thread overview]
Message-ID: <20240613114001.270233-5-alisa.roman@analog.com> (raw)
In-Reply-To: <20240613114001.270233-1-alisa.roman@analog.com>
Internal clock of AD719X devices can be made available on MCLK2 pin. Add
clock provider to support this functionality.
Signed-off-by: Alisa-Dariana Roman <alisa.roman@analog.com>
---
.../devicetree/bindings/iio/adc/adi,ad7192.yaml | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad7192.yaml b/Documentation/devicetree/bindings/iio/adc/adi,ad7192.yaml
index 3ae2f860d24c..1434d89c2880 100644
--- a/Documentation/devicetree/bindings/iio/adc/adi,ad7192.yaml
+++ b/Documentation/devicetree/bindings/iio/adc/adi,ad7192.yaml
@@ -42,13 +42,20 @@ properties:
description: |
Optionally, either a crystal can be attached externally between MCLK1 and
MCLK2 pins, or an external CMOS-compatible clock can drive the MCLK2
- pin. If absent, internal 4.92MHz clock is used.
+ pin. If absent, internal 4.92MHz clock is used, which can be made
+ available on MCLK2 pin.
clock-names:
enum:
- xtal
- mclk
+ "#clock-cells":
+ const: 0
+
+ clock-output-names:
+ maxItems: 1
+
interrupts:
maxItems: 1
@@ -204,6 +211,8 @@ examples:
spi-max-frequency = <1000000>;
spi-cpol;
spi-cpha;
+ #clock-cells = <0>;
+ clock-output-names = "ad7194_mclk";
interrupts = <25 0x2>;
interrupt-parent = <&gpio>;
aincom-supply = <&aincom>;
--
2.34.1
next prev parent reply other threads:[~2024-06-13 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 11:39 [PATCH v4 0/5] iio: adc: ad7192: Improvements Alisa-Dariana Roman
2024-06-13 11:39 ` [PATCH v4 1/5] iio: adc: ad7192: Clean up dev Alisa-Dariana Roman
2024-06-15 10:58 ` Jonathan Cameron
2024-06-13 11:39 ` [PATCH v4 2/5] dt-bindings: iio: adc: ad7192: Update clock config Alisa-Dariana Roman
2024-06-13 16:41 ` Conor Dooley
2024-06-15 11:05 ` Jonathan Cameron
2024-06-13 11:39 ` [PATCH v4 3/5] " Alisa-Dariana Roman
2024-06-13 11:40 ` Alisa-Dariana Roman [this message]
2024-06-13 16:43 ` [PATCH v4 4/5] dt-bindings: iio: adc: ad7192: Add clock provider Conor Dooley
2024-06-13 11:40 ` [PATCH v4 5/5] " Alisa-Dariana Roman
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=20240613114001.270233-5-alisa.roman@analog.com \
--to=alisadariana@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alexandru.tachici@analog.com \
--cc=alisa.roman@analog.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--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