[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <499ef047-d3fc-4d2a-ba7d-342ff08a351d@kernel.org>
Date: Mon, 13 Jan 2025 11:21:28 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Nuno Sá <noname.nuno@...il.com>,
Antoniu Miclaus <antoniu.miclaus@...log.com>
Cc: jic23@...nel.org, robh@...nel.org, conor+dt@...nel.org,
linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pwm@...r.kernel.org
Subject: Re: [PATCH v4 1/3] dt-bindings: iio: adf4371: add refin mode
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.
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?
Best regards,
Krzysztof
Powered by blists - more mailing lists