From: Jonathan Cameron <jic23@kernel.org>
To: Rodrigo Alencar via B4 Relay
<devnull+rodrigo.alencar.analog.com@kernel.org>
Cc: rodrigo.alencar@analog.com, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.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 6/6] Documentation: ABI: testing: add support for ADF41513
Date: Sun, 21 Dec 2025 17:52:49 +0000 [thread overview]
Message-ID: <20251221175249.11b5ff02@jic23-huawei> (raw)
In-Reply-To: <20251219-adf41513-iio-driver-v2-6-be29a83d5793@analog.com>
On Fri, 19 Dec 2025 12:34:53 +0000
Rodrigo Alencar via B4 Relay <devnull+rodrigo.alencar.analog.com@kernel.org> wrote:
> From: Rodrigo Alencar <rodrigo.alencar@analog.com>
>
> Add ABI documentation for ADF41513 PLL sysfs interfaces
>
> Signed-off-by: Rodrigo Alencar <rodrigo.alencar@analog.com>
Do this in the patches that add the ABI, or in a patch before them.
Also try building docs. Unless something changed recently that will
moan about duplication.
When ABI is generalized from one driver to many we have to move
the documentation (and make it generic) such that is is shared by
the relevant drivers. In this case
sysfs-bus-iio-frequency is probably the appropriate file.
> ---
> .../ABI/testing/sysfs-bus-iio-frequency-adf41513 | 27 ++++++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 28 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf41513 b/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf41513
> new file mode 100644
> index 000000000000..11ffd248eedb
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-bus-iio-frequency-adf41513
> @@ -0,0 +1,27 @@
> +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency_resolution
> +KernelVersion: 6.20
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Stores channel Y frequency resolution/channel spacing in Hz.
> + The value given directly influences the choice of operation:
> +
> + - integer-N: requested frequency is a multiple of the Phase Detector
> + frequency.
> + - fixed modulus: fractional-N mode with fixed modulus.
> + - variable modulus: dual-modulus fractional-N mode with extra variable
> + modulus added on top of the fixed one.
> +
> + It is assumed that the algorithm that is used to compute the various
> + dividers, is able to generate proper values for multiples of channel
> + spacing.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_refin_frequency
> +KernelVersion: 6.20
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Sets channel Y REFin frequency in Hz. In some clock chained
> + applications, the reference frequency used by the PLL may change during
> + runtime. This attribute allows the user to adjust the reference
> + frequency accordingly.
> + To avoid glitches in the RF output, consider using out_altvoltageY_powerdown
> + to power down the PLL and its RFOut buffers during REFin changes.
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c536c3afc1ae..48fa1011b797 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1606,6 +1606,7 @@ M: Rodrigo Alencar <rodrigo.alencar@analog.com>
> L: linux-iio@vger.kernel.org
> S: Supported
> W: https://ez.analog.com/linux-software-drivers
> +F: Documentation/ABI/testing/sysfs-bus-iio-frequency-adf41513
> F: Documentation/devicetree/bindings/iio/frequency/adi,adf41513.yaml
> F: Documentation/iio/adf41513.rst
> F: drivers/iio/frequency/adf41513.c
>
next prev parent reply other threads:[~2025-12-21 17:53 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
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 [this message]
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=20251221175249.11b5ff02@jic23-huawei \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=devnull+rodrigo.alencar.analog.com@kernel.org \
--cc=dlechner@baylibre.com \
--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