From: "Rob Herring (Arm)" <robh@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org,
"Michael Hennerich" <Michael.Hennerich@analog.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Jonathan Cameron" <jic23@kernel.org>
Subject: Re: [PATCH 1/4] dt-bindings: iio: adc: adi,ad7124: fix clocks properties
Date: Fri, 25 Jul 2025 18:27:06 -0500 [thread overview]
Message-ID: <175348602635.2026537.7901713448810166521.robh@kernel.org> (raw)
In-Reply-To: <20250724-iio-adc-ad7124-proper-clock-support-v1-1-88f35db2fcaf@baylibre.com>
On Thu, 24 Jul 2025 18:25:22 -0500, David Lechner wrote:
> Use correct clocks properties for the AD7124 family of ADCs.
>
> These ADCs have an internal clock along with an optional external clock
> that can be connected to the CLK pin. This pin can be wired up 3 ways:
> 1. Not connected - the internal clock is used.
> 2. Connected to an external clock (input) - the external clock is used.
> 3. Connected to the CLK pin on another ADC (output) - the internal clock
> is used on one and the other is configured for an external clock.
>
> The new bindings describe these 3 cases by picking one of the following:
> 1. Omit both clocks and #clock-cells properties.
> 2. Include only the clocks property with a phandle to the external clock.
> 3. Include only the #clock-cells property on the ADC providing the output.
>
> The clock-names property is now deprecated and should not be used. The
> MCLK signal that it refers to is an internal counter in the ADC and
> therefore does not make sense as a devicetree property as it can't be
> connected to anything external to the ADC. Since there is only one
> possible external clock, the clock-names property is not needed anyway.
> Based on the implementation of the Linux driver, it looks like the
> "mclk" clock was basically being used as a control to select the power
> mode of the ADC, which is not something that should be done in the
> devicetree.
>
> Signed-off-by: David Lechner <dlechner@baylibre.com>
> ---
> .../devicetree/bindings/iio/adc/adi,ad7124.yaml | 21 ++++++++++++++++-----
> 1 file changed, 16 insertions(+), 5 deletions(-)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-07-25 23:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 23:25 [PATCH 0/4] iio: adc: ad7124: proper clock support David Lechner
2025-07-24 23:25 ` [PATCH 1/4] dt-bindings: iio: adc: adi,ad7124: fix clocks properties David Lechner
2025-07-25 23:27 ` Rob Herring (Arm) [this message]
2025-07-24 23:25 ` [PATCH 2/4] iio: adc: ad7124: do not require mclk David Lechner
2025-07-27 12:21 ` Jonathan Cameron
2025-07-29 16:08 ` David Lechner
2025-07-29 18:42 ` Jonathan Cameron
2025-07-24 23:25 ` [PATCH 3/4] iio: adc: ad7124: add external clock support David Lechner
2025-07-27 12:24 ` Jonathan Cameron
2025-07-24 23:25 ` [PATCH 4/4] iio: adc: ad7124: add clock output support David Lechner
2025-07-27 12:29 ` 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=175348602635.2026537.7901713448810166521.robh@kernel.org \
--to=robh@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
/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
all inboxes | Powered by JetHome®