From: Jonathan Cameron <jic23@kernel.org>
To: linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [RFC PATCH 0/7] IIO ABI documentation duplication fixes
Date: Sun, 21 Feb 2021 16:12:22 +0000 [thread overview]
Message-ID: <20210221161222.49946f14@archlinux> (raw)
In-Reply-To: <20210117153816.696693-1-jic23@kernel.org>
On Sun, 17 Jan 2021 15:38:09 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Hi All,
Suffering from "maintainer's" curse on these of there being no one I can
generically moan at over lack of reviews :) If someone could just
cast their eyes over patches 1, 3, 4 and 7 to check I haven't done anything
exceedingly stupid that would be great.
Thanks,
Jonathan
>
> The nature of IIO devices is that they are highly varied and occaisonly
> ABI is used in somewhat of a 'best fit' fashion. This has lead to a
> situation where we had additional more specific ABI docs for some sysfs
> parameters in certain drivers. Unfortunately the automated documentation
> building doesn't work well with this both issuing warnings and building
> a less than ideal output.
>
> So this series attempts to fix that up, mostly by moving the application
> specific parts, of properties that are documented in more than one place,
> into a higher level documentation file, sometimes with a device specific
> note. In a few cases this the result is a bit non-obvious hence the RFC.
> Roughly speaking I've put the more 'interesting' cases towards the end
> of the series.
>
> It's worth noting that a general reorganzation, audit of missing docs
> etc is needed for the IIO ABI docs, but as that's a big job it may well
> take sometime to get it done. In the meantime let's deal with these
> issues. Some of the drivers have complex enough ABI that we should probably
> have detailed docs for them in addition to Documentation/ABI.
>
> Note I haven't yet touched the remaining case of
> Warning: /sys/bus/iio/devices/iio:deviceX/in_count0_preset is defined 2 times: ./Documentation/ABI/testing/sysfs-bus-iio-timer-stm32:100 ./Documentation/ABI/testing/sysfs-bus-iio-lptimer-stm32:0
> Warning: /sys/bus/iio/devices/iio:deviceX/in_count_quadrature_mode_available is defined 2 times: ./Documentation/ABI/testing/sysfs-bus-iio-counter-104-quad-8:2 ./Documentation/ABI/testing/sysfs-bus-iio-lptimer-stm32:8
>
> This is mainly because I don't really know enough about these devices
> to conclude exactly what a fused bit of docs should look like.
> Also worth noting that those are probably deprecated ABI anyway given
> the move of counters into their own subsystem.
>
> Jonathan Cameron (7):
> iio:ABI docs: Fix up duplicate *_calibbias_* documentation for
> icm42600
> iio:ABI docs: Avoid repitition of triggerX/sampling_frequency
> iio:ABI docs: Drop device specific docs for _powerdown for the adf4371
> iio:ABI docs: Fix issue around repeated definition of out_currentY_raw
> iio:ABI docs: Combine sysfs-bus-iio-humidity-hdc2010/hdc100x into one
> file
> iio:ABI docs: Combine the two instances of docs for sensor_sensitivity
> iio:ABI docs: Move specific description of out_altvoltageX_frequency
> to main docs.
>
> Documentation/ABI/testing/sysfs-bus-iio | 45 +++++++++++++++++++
> .../ABI/testing/sysfs-bus-iio-distance-srf08 | 8 ----
> .../testing/sysfs-bus-iio-frequency-adf4371 | 33 --------------
> .../ABI/testing/sysfs-bus-iio-health-afe440x | 10 +----
> ...umidity-hdc2010 => sysfs-bus-iio-humidity} | 3 +-
> .../testing/sysfs-bus-iio-humidity-hdc100x | 9 ----
> .../ABI/testing/sysfs-bus-iio-icm42600 | 20 ---------
> .../testing/sysfs-bus-iio-light-lm3533-als | 11 ++---
> .../ABI/testing/sysfs-bus-iio-proximity | 14 ++++++
> .../testing/sysfs-bus-iio-proximity-as3935 | 9 ----
> .../ABI/testing/sysfs-bus-iio-timer-stm32 | 8 ----
> 11 files changed, 66 insertions(+), 104 deletions(-)
> rename Documentation/ABI/testing/{sysfs-bus-iio-humidity-hdc2010 => sysfs-bus-iio-humidity} (79%)
> delete mode 100644 Documentation/ABI/testing/sysfs-bus-iio-humidity-hdc100x
> delete mode 100644 Documentation/ABI/testing/sysfs-bus-iio-icm42600
>
prev parent reply other threads:[~2021-02-21 16:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 15:38 [RFC PATCH 0/7] IIO ABI documentation duplication fixes Jonathan Cameron
2021-01-17 15:38 ` [RFC PATCH 1/7] iio:ABI docs: Fix up duplicate *_calibbias_* documentation for icm42600 Jonathan Cameron
2021-02-21 16:05 ` Jonathan Cameron
2021-04-27 17:30 ` Jonathan Cameron
2021-01-17 15:38 ` [RFC PATCH 2/7] iio:ABI docs: Avoid repitition of triggerX/sampling_frequency Jonathan Cameron
2021-01-18 9:02 ` Fabrice Gasnier
2021-03-07 9:40 ` Lars-Peter Clausen
2021-03-07 12:04 ` Jonathan Cameron
2021-03-12 16:56 ` Fabrice Gasnier
2021-03-15 10:12 ` Jonathan Cameron
2021-01-17 15:38 ` [RFC PATCH 3/7] iio:ABI docs: Drop device specific docs for _powerdown for the adf4371 Jonathan Cameron
2021-04-27 17:33 ` Jonathan Cameron
2021-01-17 15:38 ` [RFC PATCH 4/7] iio:ABI docs: Fix issue around repeated definition of out_currentY_raw Jonathan Cameron
2021-04-27 17:35 ` Jonathan Cameron
2021-01-17 15:38 ` [RFC PATCH 5/7] iio:ABI docs: Combine sysfs-bus-iio-humidity-hdc2010/hdc100x into one file Jonathan Cameron
2021-01-17 23:12 ` Matt Ranostay
2021-02-21 16:08 ` Jonathan Cameron
2021-01-17 15:38 ` [RFC PATCH 6/7] iio:ABI docs: Combine the two instances of docs for sensor_sensitivity Jonathan Cameron
2021-01-17 23:11 ` Matt Ranostay
2021-01-17 15:38 ` [RFC PATCH 7/7] iio:ABI docs: Move specific description of out_altvoltageX_frequency to main docs Jonathan Cameron
2021-04-27 17:37 ` Jonathan Cameron
2021-02-21 16:12 ` 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=20210221161222.49946f14@archlinux \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=lars@metafoo.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mchehab+huawei@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).