From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Alexandru Ardelean <alexandru.ardelean@analog.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-iio@vger.kernel.org>,
<lars@metafoo.de>, <Michael.Hennerich@analog.com>,
<jic23@kernel.org>, <nuno.sa@analog.com>,
<dragos.bogdan@analog.com>, Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2 1/5] iio: Documentation: update definitions for bufferY and scan_elements
Date: Thu, 1 Apr 2021 15:44:08 +0200 [thread overview]
Message-ID: <20210401154408.5f26a3c6@coco.lan> (raw)
In-Reply-To: <20210217083438.37865-2-alexandru.ardelean@analog.com>
Em Wed, 17 Feb 2021 10:34:34 +0200
Alexandru Ardelean <alexandru.ardelean@analog.com> escreveu:
> Since the new change to the IIO buffer infrastructure, the buffer/ and
> scan_elements/ directories have been merged into bufferY/ to have some
> attributes available per-buffer.
>
> This change updates the ABI docs to reflect this change.
>
> The hwfifo attributes are not updated, as for now these should be used
> via the legacy buffer/ directory until they are moved into core.
>
> Signed-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
> ---
> Documentation/ABI/testing/sysfs-bus-iio | 85 +++++++++++++++++++++++++
> 1 file changed, 85 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
> index d957f5da5c04..f2a72d7fbacb 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio
> +++ b/Documentation/ABI/testing/sysfs-bus-iio
> @@ -1118,12 +1118,16 @@ Description:
>
> What: /sys/bus/iio/devices/iio:deviceX/buffer/length
> KernelVersion: 2.6.35
> +What: /sys/bus/iio/devices/iio:deviceX/bufferY/length
> +KernelVersion: 5.11
> Contact: linux-iio@vger.kernel.org
> Description:
> Number of scans contained by the buffer.
The ABI parser doesn't like things like this:
$ ./scripts/get_abi.pl validate
Warning: file Documentation/ABI/testing/sysfs-bus-iio#1167:
What '/sys/bus/iio/devices/iio:deviceX/buffer/length' doesn't have a description
The main reason is that all properties, including KernelVersion,
Contact and Description are associated to a group of properties.
To be frank, for me that don't work with IIO, the above ABI
description doesn't sound clear.
I mean, what's the difference between
/sys/bus/iio/devices/iio:deviceX/buffer/length
and
/sys/bus/iio/devices/iio:deviceX/bufferY/length?
If the intention is to tell that:
/sys/bus/iio/devices/iio:deviceX/buffer/length
was obsoleted by:
/sys/bus/iio/devices/iio:deviceX/bufferY/length
IMO, the right thing would be to move the deprecated definition to
Documentation/ABI/obsolete/
If, on the other hand, both are completely identical and
non-obsoleted, why to have both APIs?
Or did you just missed adding a different description for the
new ABI symbols, but this was dropped due to some merge
conflict?
Thanks,
Mauro
next prev parent reply other threads:[~2021-04-01 18:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 8:34 [PATCH v2 0/5] iio: Add output buffer support Alexandru Ardelean
2021-02-17 8:34 ` [PATCH v2 1/5] iio: Documentation: update definitions for bufferY and scan_elements Alexandru Ardelean
2021-02-18 12:19 ` Jonathan Cameron
2021-02-18 13:36 ` Jonathan Cameron
2021-04-01 13:44 ` Mauro Carvalho Chehab [this message]
2021-04-01 15:00 ` Jonathan Cameron
2021-02-17 8:34 ` [PATCH v2 2/5] iio: Add output buffer support Alexandru Ardelean
2021-02-18 13:42 ` Jonathan Cameron
2021-02-19 8:45 ` Alexandru Ardelean
2021-02-17 8:34 ` [PATCH v2 3/5] iio: kfifo-buffer: " Alexandru Ardelean
2021-02-17 8:34 ` [PATCH v2 4/5] iio: triggered-buffer: extend support to configure output buffers Alexandru Ardelean
2021-02-17 8:34 ` [PATCH v2 5/5] iio: dac: ad5686: Add PWM as a trigger source Alexandru Ardelean
2021-02-18 14:05 ` Jonathan Cameron
2021-02-18 14:35 ` Rob Herring
2021-02-19 8:49 ` Alexandru Ardelean
2021-02-23 16:37 ` Lars-Peter Clausen
2021-02-27 15:45 ` Jonathan Cameron
2021-02-18 13:38 ` [PATCH v2 0/5] iio: Add output buffer 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=20210401154408.5f26a3c6@coco.lan \
--to=mchehab+huawei@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=dragos.bogdan@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@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