From: "Nuno Sá" <noname.nuno@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
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 v4 1/3] dt-bindings: iio: adf4371: add refin mode
Date: Mon, 13 Jan 2025 11:17:18 +0000 [thread overview]
Message-ID: <98dad0cd3ba55411797c1871c5ceb5f656b8225b.camel@gmail.com> (raw)
In-Reply-To: <499ef047-d3fc-4d2a-ba7d-342ff08a351d@kernel.org>
On Mon, 2025-01-13 at 11:21 +0100, Krzysztof Kozlowski wrote:
> On 13/01/2025 10:55, Nuno Sá wrote:
> > On Mon, 2025-01-13 at 09:37 +0100, Krzysztof Kozlowski wrote:
> > > On Thu, Jan 09, 2025 at 03:37:05PM +0200, Antoniu Miclaus wrote:
> > > > 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
> > >
> > > Which pins are these? I went through adf4371 datasheet and no reference
> > > on clock inputs like clkin or clkin-diff.
> > >
> > >
> >
> > Hmm, I guess we should call this 'refp' and 'refp-n' then (the latter seems
> > a
> > bit more odd)? Or just 'ref' and 'ref-diff'?
>
> That mistake was done at the beginning - the "clkin" is just useless
> name. It cannot be "clkout" and it cannot be anything else than clk, so
> it is 100% redundant.
>
Oh sure... Makes sense and I forgot that the property is not new...
> But looking for pins brought second point - here you claim these are
> mutually exclusive while datasheet suggests that both inputs can be
> connected. Unless they come from the same source always?
>
If you have a single ended input then only one pin (the positive one) will be
used. If the input signal is differential, then both pins will be used. So they
are mutually exclusive... You either have single ended or a differential input.
And depending on the input type, the limit of the input frequency varies.
- Nuno Sá
next prev parent reply other threads:[~2025-01-13 11:17 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
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á [this message]
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=98dad0cd3ba55411797c1871c5ceb5f656b8225b.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk@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