devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: jic23@kernel.org, robh@kernel.org, conor+dt@kernel.org,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: frequency: adf4377: add clk provider
Date: Mon, 17 Nov 2025 19:19:01 +0000	[thread overview]
Message-ID: <20251117-cloning-nickname-16a95d4b0795@spud> (raw)
In-Reply-To: <20251114115923.6043-2-antoniu.miclaus@analog.com>

[-- Attachment #1: Type: text/plain, Size: 1728 bytes --]

On Fri, Nov 14, 2025 at 11:59:22AM +0000, Antoniu Miclaus wrote:
> Add support for clock provider.
> 
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---
>  .../bindings/iio/frequency/adi,adf4377.yaml   | 20 +++++++++++++++++++
>  1 file changed, 20 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/iio/frequency/adi,adf4377.yaml b/Documentation/devicetree/bindings/iio/frequency/adi,adf4377.yaml
> index 5f950ee9aec7..dab1591a36b3 100644
> --- a/Documentation/devicetree/bindings/iio/frequency/adi,adf4377.yaml
> +++ b/Documentation/devicetree/bindings/iio/frequency/adi,adf4377.yaml
> @@ -40,6 +40,12 @@ properties:
>      items:
>        - const: ref_in
>  
> +  '#clock-cells':
> +    const: 0
> +
> +  clock-output-names:
> +    maxItems: 1
> +
>    chip-enable-gpios:
>      description:
>        GPIO that controls the Chip Enable Pin.
> @@ -99,4 +105,18 @@ examples:
>              clock-names = "ref_in";
>          };
>      };
> +  - |
> +    spi {
> +        #address-cells = <1>;
> +        #size-cells = <0>;
> +        frequency@0 {
> +            compatible = "adi,adf4378";
> +            reg = <0>;
> +            spi-max-frequency = <10000000>;
> +            clocks = <&adf4378_ref_in>;
> +            clock-names = "ref_in";
> +            #clock-cells = <0>;
> +            clock-output-names = "adf4378_clk";

Why's the point of having "_clk" in a clock name?
Also, not sure you need a new example for this, could just put them in
the other example, no?

Drop the _clk at least, and then
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: changes-requested

> +        };
> +    };
>  ...
> -- 
> 2.43.0
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-11-17 19:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 11:59 [PATCH 0/2] iio: frequency: adf4377: add clock provider support Antoniu Miclaus
2025-11-14 11:59 ` [PATCH 1/2] dt-bindings: frequency: adf4377: add clk provider Antoniu Miclaus
2025-11-17 19:19   ` Conor Dooley [this message]
2025-11-14 11:59 ` [PATCH 2/2] iio: frequency: adf4377: add clk provider support Antoniu Miclaus
  -- strict thread matches above, loose matches on Subject: below --
2025-11-14 12:09 [PATCH 0/2] iio: frequency: adf4377: add clock " Antoniu Miclaus
2025-11-14 12:09 ` [PATCH 1/2] dt-bindings: frequency: adf4377: add clk provider Antoniu Miclaus
2025-11-15 17: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=20251117-cloning-nickname-16a95d4b0795@spud \
    --to=conor@kernel.org \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --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).