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, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: adf4371: add rdiv2 and doubler
Date: Mon, 25 Nov 2024 18:23:53 +0000 [thread overview]
Message-ID: <20241125-rotting-brim-162582b5ad42@spud> (raw)
In-Reply-To: <20241125112643.10459-2-antoniu.miclaus@analog.com>
[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]
On Mon, Nov 25, 2024 at 01:26:40PM +0200, Antoniu Miclaus wrote:
> Add support for reference doubler enable and reference divide by 2
> clock.
You're still missing an explanation here for why these cannot be derived
from the required output frequency vs the input frequency.
>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---
> no changes in v2. (added cover letter as requested)
> .../devicetree/bindings/iio/frequency/adf4371.yaml | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/frequency/adf4371.yaml b/Documentation/devicetree/bindings/iio/frequency/adf4371.yaml
> index 1cb2adaf66f9..ef241c38520c 100644
> --- a/Documentation/devicetree/bindings/iio/frequency/adf4371.yaml
> +++ b/Documentation/devicetree/bindings/iio/frequency/adf4371.yaml
> @@ -40,6 +40,17 @@ properties:
> output stage will shut down until the ADF4371/ADF4372 achieves lock as
> measured by the digital lock detect circuitry.
>
> + adi,reference-doubler-enable:
> + type: boolean
> + description:
> + If this property is present, the reference doubler block is enabled.
> +
> + adi,adi,reference-div2-enable:
> + type: boolean
> + description:
> + If this property is present, the reference divide by 2 clock is enabled.
> + This feature can be used to provide a 50% duty cycle signal to the PFD.
> +
> required:
> - compatible
> - reg
> --
> 2.47.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-11-25 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 11:26 [PATCH v2 0/2] Add ADF4371 Reference Doubler and Reference Divider Antoniu Miclaus
2024-11-25 11:26 ` [PATCH v2 1/2] dt-bindings: iio: adf4371: add rdiv2 and doubler Antoniu Miclaus
2024-11-25 18:23 ` Conor Dooley [this message]
2024-11-25 11:26 ` [PATCH v2 2/2] iio: frequency: adf4371: add ref doubler and div2 Antoniu Miclaus
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=20241125-rotting-brim-162582b5ad42@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=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