public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: <robh@kernel.org>, <conor+dt@kernel.org>,
	<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-pwm@vger.kernel.org>
Subject: Re: [PATCH v4 1/3] dt-bindings: iio: adf4371: add refin mode
Date: Sun, 12 Jan 2025 15:01:48 +0000	[thread overview]
Message-ID: <20250112150148.43349803@jic23-huawei> (raw)
In-Reply-To: <20250109133707.3845-2-antoniu.miclaus@analog.com>

On Thu, 9 Jan 2025 15:37:05 +0200
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:

> Add support for selecting between single-ended and differential
> reference input.
> 
> By default the single-ended input is enabled.
> 
> Input frequency boundaries are change based on the mode selected
> (single-ended/differential).
> 
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---
> changes in v4:
>  - add enum in clock-names to support both se and diff input.
>  .../devicetree/bindings/iio/frequency/adf4371.yaml         | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/iio/frequency/adf4371.yaml b/Documentation/devicetree/bindings/iio/frequency/adf4371.yaml
> index 1cb2adaf66f9..9ad5b22c59d7 100644
> --- a/Documentation/devicetree/bindings/iio/frequency/adf4371.yaml
> +++ b/Documentation/devicetree/bindings/iio/frequency/adf4371.yaml
> @@ -30,8 +30,11 @@ properties:
>  
>    clock-names:
>      description:
> -      Must be "clkin"
> -    maxItems: 1
> +      Must be "clkin" if the input reference is single ended or "clkin-diff"
> +      if the input reference is differential. By default single ended input is
> +      applied.
> +    enum: [clkin, clkin-diff]
> +    default: clkin
Given the property is required, what does a default mean?

I don't think you want to apply a default, or mention it in the description.
Otherwise LGTM.

>  
>    adi,mute-till-lock-en:
>      type: boolean


  reply	other threads:[~2025-01-12 15:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 13:37 [PATCH v4 0/3] ADF4371 refin mode and doubler support Antoniu Miclaus
2025-01-09 13:37 ` [PATCH v4 1/3] dt-bindings: iio: adf4371: add refin mode Antoniu Miclaus
2025-01-12 15:01   ` Jonathan Cameron [this message]
2025-01-13  8:37   ` Krzysztof Kozlowski
2025-01-13  9:55     ` Nuno Sá
2025-01-13 10:08       ` Miclaus, Antoniu
2025-01-13 10:21       ` Krzysztof Kozlowski
2025-01-13 11:17         ` Nuno Sá
2025-01-13 11:24           ` Krzysztof Kozlowski
2025-01-13 11:50             ` Miclaus, Antoniu
2025-01-13 12:05               ` Krzysztof Kozlowski
2025-01-13 20:18                 ` Jonathan Cameron
2025-01-09 13:37 ` [PATCH v4 2/3] iio: frequency: " Antoniu Miclaus
2025-01-13  9:57   ` Nuno Sá
2025-01-13  9:59     ` Nuno Sá
2025-01-09 13:37 ` [PATCH v4 3/3] iio: frequency: adf4371: add ref doubler Antoniu Miclaus
2025-01-13 10:01   ` Nuno Sá
2025-01-12 15:02 ` [PATCH v4 0/3] ADF4371 refin mode and doubler support 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=20250112150148.43349803@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pwm@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