From: Jonathan Cameron <jic23@kernel.org>
To: Rodrigo Alencar <455.rodrigo.alencar@gmail.com>
Cc: Rodrigo Alencar via B4 Relay
<devnull+rodrigo.alencar.analog.com@kernel.org>,
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 v6 8/8] Documentation: ABI: testing: add common ABI file for iio/frequency
Date: Sat, 14 Feb 2026 14:44:53 +0000 [thread overview]
Message-ID: <20260214144453.349fc0a1@jic23-huawei> (raw)
In-Reply-To: <ecfpri6dr4kidvecyulzip7m2bmuw5refocls7vdtruqinrklc@dzm5vmk7ul5r>
On Wed, 11 Feb 2026 13:52:18 +0000
Rodrigo Alencar <455.rodrigo.alencar@gmail.com> wrote:
> On 26/02/07 05:24PM, Jonathan Cameron wrote:
> > On Fri, 30 Jan 2026 10:06:49 +0000
> > Rodrigo Alencar via B4 Relay <devnull+rodrigo.alencar.analog.com@kernel.org> wrote:
> >
> > > From: Rodrigo Alencar <rodrigo.alencar@analog.com>
> > >
> > > Add ABI documentation file for PLL/DDS devices with frequency_resolution
> > > sysfs entry attribute used by ADF4350 and ADF41513.
>
> Here it mentions that this would also work for ADF4350.
>
> > >
> > > Signed-off-by: Rodrigo Alencar <rodrigo.alencar@analog.com>
> > > ---
> > > Documentation/ABI/testing/sysfs-bus-iio-frequency | 11 +++++++++++
> > > MAINTAINERS | 1 +
> > > 2 files changed, 12 insertions(+)
> > >
> > > diff --git a/Documentation/ABI/testing/sysfs-bus-iio-frequency b/Documentation/ABI/testing/sysfs-bus-iio-frequency
> > > new file mode 100644
> > > index 000000000000..1ce8ae578fd6
> > > --- /dev/null
> > > +++ b/Documentation/ABI/testing/sysfs-bus-iio-frequency
> > > @@ -0,0 +1,11 @@
> > > +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 for PLL
> > > + devices. The given value directly influences the operating mode when
> > > + fractional-N synthesis is required, as it derives values for
> > > + configurable modulus parameters used in the calculation of the output
> > > + frequency. 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.
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 0d9b7cf86aec..748eeb6f5bd2 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -1639,6 +1639,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
> > I wouldn't add this here. Whilst for now we only use the defined
> > ABI in this one driver, I'd not expect it to stay that way.
> >
> > If we do think it is very drive specific move the file to
> > sysfs-bus-iio-frequency-adf41513
>
> The file Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350
> contains the same ABI description, should that be removed there
> in favor or this one? If so, in MAINTAINERS, what is the best place
> for this ABI file?
For sysfs ABI we can't have repeats in multiple files (it breaks the
docs generation IIRC). So if we have it used in multiple drivers
then it needs to go in the more generic files as you have it.
For maintainers, either don't bother with an explicit entry (the subsystem
ones will catch it) or add I suppose we could have one for
drivers/iio/frequency/ that calls out this specific file + all the drivers
in that directory. I'm not sure that's worthwhile - so I'd go with just
not listing it (ignore the checkpatch warning).
Jonathan
> If not, for simplicity, I may just rename the file to
> sysfs-bus-iio-frequency-adf41513, as you suggested.
>
prev parent reply other threads:[~2026-02-14 14:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 10:06 [PATCH v6 0/8] ADF41513/ADF41510 PLL frequency synthesizers Rodrigo Alencar via B4 Relay
2026-01-30 10:06 ` [PATCH v6 1/8] dt-bindings: iio: frequency: add adf41513 Rodrigo Alencar via B4 Relay
2026-01-30 10:06 ` [PATCH v6 2/8] iio: core: add fixed point parsing with 64-bit parts Rodrigo Alencar via B4 Relay
2026-02-02 9:57 ` Nuno Sá
2026-02-03 9:26 ` Rodrigo Alencar
2026-02-03 10:04 ` Nuno Sá
2026-02-07 16:59 ` Jonathan Cameron
2026-02-04 1:45 ` Andy Shevchenko
2026-02-04 9:42 ` Rodrigo Alencar
2026-02-04 9:57 ` Andy Shevchenko
2026-02-04 10:28 ` Rodrigo Alencar
2026-02-04 10:34 ` Andy Shevchenko
2026-02-07 17:02 ` Jonathan Cameron
2026-02-08 13:24 ` Andy Shevchenko
2026-01-30 10:06 ` [PATCH v6 3/8] iio: test: add kunit test for fixed-point parsing Rodrigo Alencar via B4 Relay
2026-02-03 15:38 ` Andy Shevchenko
2026-01-30 10:06 ` [PATCH v6 4/8] iio: frequency: adf41513: driver implementation Rodrigo Alencar via B4 Relay
2026-02-07 17:21 ` Jonathan Cameron
2026-01-30 10:06 ` [PATCH v6 5/8] iio: frequency: adf41513: handle LE synchronization feature Rodrigo Alencar via B4 Relay
2026-01-30 10:06 ` [PATCH v6 6/8] iio: frequency: adf41513: features on frequency change Rodrigo Alencar via B4 Relay
2026-01-30 10:06 ` [PATCH v6 7/8] docs: iio: add documentation for adf41513 driver Rodrigo Alencar via B4 Relay
2026-01-30 10:06 ` [PATCH v6 8/8] Documentation: ABI: testing: add common ABI file for iio/frequency Rodrigo Alencar via B4 Relay
2026-02-07 17:24 ` Jonathan Cameron
2026-02-11 13:52 ` Rodrigo Alencar
2026-02-14 14:44 ` Jonathan Cameron [this message]
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=20260214144453.349fc0a1@jic23-huawei \
--to=jic23@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=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