public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: 455.rodrigo.alencar@gmail.com,
	Rodrigo Alencar <rodrigo.alencar@analog.com>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
	devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
	Jonathan Cameron <jic23@kernel.org>,
	David Lechner <dlechner@baylibre.com>,
	Andy Shevchenko <andy@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH v2 1/6] dt-bindings: iio: frequency: add adf41513
Date: Sun, 21 Dec 2025 14:02:51 +0100	[thread overview]
Message-ID: <326c3e83-059e-4e96-ab99-d4a33eb3b56f@kernel.org> (raw)
In-Reply-To: <gz36kmewv4bhwqz6d3xqatcx65uzukqcgsvfbwhr7c3yhw225z@edeggfhjws2h>

On 20/12/2025 19:05, 455.rodrigo.alencar@gmail.com wrote:
> Hi Krzystof,
> 
> thanks for taking a look into this again. It was my first patch it didn't want
> to draw more attention or discussion to the V1 patch as it was declared not ready
> at its very first review.
> 
> On 25/12/20 10:21AM, Krzysztof Kozlowski wrote:
>> On Fri, Dec 19, 2025 at 12:34:48PM +0000, Rodrigo Alencar wrote:
>>> dt-bindings for ADF41513, an ultralow noise PLL frequency synthesizer that
>>> can be used to implement local oscillators (LOs) as high as 26.5 GHz.
>>> Most properties refer to existing PLL driver properties (e.g. ADF4350).
>>
>> What is "existing PLL driver"? I know about motor drivers, but can you
>> drive PLL?
>>
>> And how is ADF4350 related to this binding. I do not see ADF4350
>> compatible here at all. Describe hardware, a real one.
> 
> ADF4350 is an older one, and its bindings can be found at:
> Documentation/devicetree/bindings/iio/frequency/adi,adf4350.yaml
> It is a similar part, but yet very different.
> 
>>
>> Nothing improved.
>>
>> You ignored comments, did not bother to respond to them and then sent
>> the same.
> 
> Sorry for not responding on the V1 thread, but the previous patch had to be reviewed internally
> first. It is not true that nothing is improved, in fact, it has changed a lot, here are some notes:

Process is not like that. You first review internally, then you send.
After you sent and receive comments, you respond to these comments.

> * adi,power-up-frequency is not carrying the -hz postfix because it forces to be a uint32 by
> the dt-bindings check. For that variable it needs to be uint64 as the part supports up to 26.5 GHz > 2^32

And what granularity do you need? Why mhz does not work?

> * The properties related to the reference input signal path: reference-div-factor, reference-doubler-enable
> reference-div2-enable are declared here because they are constraints for the PFD frequency definition,
> which is the frequency that the output signal is updated, important for the loop-filter and VCO design.
> * added support for all different power supply regulators.

Sorry, but I cannot respond that way. We discuss inline, so I have
entire picture, not some parts of message semi-quoted here. I don't
remember what was there and I am not going to keep looking for that.

You need to adjust to mailing list discussion style, not introduce the
others. I have just way too many other patches to deal with, so
implement the feedback or respond properly.

Best regards,
Krzysztof

  reply	other threads:[~2025-12-21 13:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 12:34 [PATCH v2 0/6] ADF41513/ADF41510 PLL frequency synthesizers Rodrigo Alencar via B4 Relay
2025-12-19 12:34 ` [PATCH v2 1/6] dt-bindings: iio: frequency: add adf41513 Rodrigo Alencar via B4 Relay
2025-12-20  9:21   ` Krzysztof Kozlowski
2025-12-20 18:05     ` 455.rodrigo.alencar
2025-12-21 13:02       ` Krzysztof Kozlowski [this message]
2025-12-22 10:21         ` Rodrigo Alencar
2025-12-21 15:56       ` Jonathan Cameron
2025-12-21 19:56         ` Rodrigo Alencar
2025-12-21 16:59   ` Jonathan Cameron
2025-12-21 19:45     ` Rodrigo Alencar
2025-12-27 16:51       ` Jonathan Cameron
2025-12-19 12:34 ` [PATCH v2 2/6] iio: frequency: adf41513: driver implementation Rodrigo Alencar via B4 Relay
2025-12-21 17:49   ` Jonathan Cameron
2025-12-22  9:45     ` Rodrigo Alencar
2025-12-27 16:56       ` Jonathan Cameron
2025-12-19 12:34 ` [PATCH v2 3/6] iio: frequency: adf41513: handle LE synchronization feature Rodrigo Alencar via B4 Relay
2025-12-19 12:34 ` [PATCH v2 4/6] iio: frequency: adf41513: features on frequency change Rodrigo Alencar via B4 Relay
2025-12-19 12:34 ` [PATCH v2 5/6] docs: iio: add documentation for adf41513 driver Rodrigo Alencar via B4 Relay
2025-12-21 18:00   ` Jonathan Cameron
2025-12-21 20:20     ` Rodrigo Alencar
2025-12-27 17:06       ` Jonathan Cameron
2025-12-19 12:34 ` [PATCH v2 6/6] Documentation: ABI: testing: add support for ADF41513 Rodrigo Alencar via B4 Relay
2025-12-21 17:52   ` Jonathan Cameron
2025-12-22  9:24     ` Rodrigo Alencar

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=326c3e83-059e-4e96-ab99-d4a33eb3b56f@kernel.org \
    --to=krzk@kernel.org \
    --cc=455.rodrigo.alencar@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=rodrigo.alencar@analog.com \
    /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