From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Navin Sankar Velliangiri <navin@linumiz.com>,
Paresh Chaudhary <paresh.chaudhary@rockwellcollins.com>
Subject: Re: [PATCH 1/4] iio: ABI: temperature: Unify documentation for thermocouple fault detection.
Date: Sun, 26 Jun 2022 23:33:31 +0100 [thread overview]
Message-ID: <20220626233331.2e8e38d1@sal.lan> (raw)
In-Reply-To: <20220626165511.602202-2-jic23@kernel.org>
Em Sun, 26 Jun 2022 17:55:08 +0100
Jonathan Cameron <jic23@kernel.org> escreveu:
> From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> The kernel build docs do not support having multiple definitions for
> the same sysfs filename.
Actually, this is not a matter of the docs build system not supporting.
It is, instead, how the ABI were supposed to work: a given ABI symbol
should have consistent behavior on all drivers that use it. Failing to
do that is asking for troubles.
So, having duplicated symbols either mean that:
a) both have the same meaning. They can/should be unified in order to
remove redundant documentation;
b) the same ABI symbol have different meanings depending on the driver(s)
that use it. This makes very hard for userspace, as it is harder to
write a program using it, as the behavior/meaning starts to be
driver-dependent.
> Hence generalize the documentation a little
> and pull it out of device specific files and into
> sysfs-bus-iio-thermocouple
>
> These may well be more general and need pulling into a more generic
> file in the future, but we can do that when it is needed.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Cc: Navin Sankar Velliangiri <navin@linumiz.com>
> Cc: Paresh Chaudhary <paresh.chaudhary@rockwellcollins.com>
Except for the above correction, the patch looks OK to me.
Reviewed-by: Mauro Carvalho Chehab <mchehab@kernel.org>
> ---
> .../sysfs-bus-iio-temperature-max31856 | 31 -------------------
> .../sysfs-bus-iio-temperature-max31865 | 12 -------
> .../ABI/testing/sysfs-bus-iio-thermocouple | 18 +++++++++++
> 3 files changed, 18 insertions(+), 43 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio-temperature-max31856 b/Documentation/ABI/testing/sysfs-bus-iio-temperature-max31856
> deleted file mode 100644
> index e5ef6d8e5da1..000000000000
> --- a/Documentation/ABI/testing/sysfs-bus-iio-temperature-max31856
> +++ /dev/null
> @@ -1,31 +0,0 @@
> -What: /sys/bus/iio/devices/iio:deviceX/fault_oc
> -KernelVersion: 5.1
> -Contact: linux-iio@vger.kernel.org
> -Description:
> - Open-circuit fault. The detection of open-circuit faults,
> - such as those caused by broken thermocouple wires.
> - Reading returns either '1' or '0'.
> -
> - === =======================================================
> - '1' An open circuit such as broken thermocouple wires
> - has been detected.
> - '0' No open circuit or broken thermocouple wires are detected
> - === =======================================================
> -
> -What: /sys/bus/iio/devices/iio:deviceX/fault_ovuv
> -KernelVersion: 5.1
> -Contact: linux-iio@vger.kernel.org
> -Description:
> - Overvoltage or Undervoltage Input Fault. The internal circuitry
> - is protected from excessive voltages applied to the thermocouple
> - cables by integrated MOSFETs at the T+ and T- inputs, and the
> - BIAS output. These MOSFETs turn off when the input voltage is
> - negative or greater than VDD.
> -
> - Reading returns either '1' or '0'.
> -
> - === =======================================================
> - '1' The input voltage is negative or greater than VDD.
> - '0' The input voltage is positive and less than VDD (normal
> - state).
> - === =======================================================
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio-temperature-max31865 b/Documentation/ABI/testing/sysfs-bus-iio-temperature-max31865
> index 4b072da92218..349089e4f2d6 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio-temperature-max31865
> +++ b/Documentation/ABI/testing/sysfs-bus-iio-temperature-max31865
> @@ -1,15 +1,3 @@
> -What: /sys/bus/iio/devices/iio:deviceX/fault_ovuv
> -KernelVersion: 5.11
> -Contact: linux-iio@vger.kernel.org
> -Description:
> - Overvoltage or Undervoltage Input fault. The internal circuitry
> - is protected from excessive voltages applied to the thermocouple
> - cables at FORCE+, FORCE2, RTDIN+ & RTDIN-. This circuitry turn
> - off when the input voltage is negative or greater than VDD.
> -
> - Reading returns '1' if input voltage is negative or greater
> - than VDD, otherwise '0'.
> -
> What: /sys/bus/iio/devices/iio:deviceX/in_filter_notch_center_frequency
> KernelVersion: 5.11
> Contact: linux-iio@vger.kernel.org
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio-thermocouple b/Documentation/ABI/testing/sysfs-bus-iio-thermocouple
> new file mode 100644
> index 000000000000..01259df297ca
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-bus-iio-thermocouple
> @@ -0,0 +1,18 @@
> +What: /sys/bus/iio/devices/iio:deviceX/fault_ovuv
> +KernelVersion: 5.1
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Overvoltage or Undervoltage Input Fault. The internal circuitry
> + is protected from excessive voltages applied to the thermocouple
> + cables. The device can also detect if such a condition occurs.
> +
> + Reading returns '1' if input voltage is negative or greater
> + than VDD, otherwise '0'.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/fault_oc
> +KernelVersion: 5.1
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Open-circuit fault. The detection of open-circuit faults,
> + such as those caused by broken thermocouple wires.
> + Reading returns '1' if fault, '0' otherwise.
next prev parent reply other threads:[~2022-06-26 22:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 16:55 [PATCH 0/4] IIO: Some documentation error and warning fixes Jonathan Cameron
2022-06-26 16:55 ` [PATCH 1/4] iio: ABI: temperature: Unify documentation for thermocouple fault detection Jonathan Cameron
2022-06-26 22:33 ` Mauro Carvalho Chehab [this message]
2022-06-27 14:18 ` Jonathan Cameron
2022-06-28 6:44 ` Mauro Carvalho Chehab
2022-07-18 17:36 ` Jonathan Cameron
2022-06-26 16:55 ` [PATCH 2/4] iio: ABI: max31865: Drop in_filter_notch_centre_frequency as in main docs Jonathan Cameron
2022-06-26 22:35 ` Mauro Carvalho Chehab
2022-06-26 16:55 ` [PATCH 3/4] iio: ABI: stm32-timer-trigger: Fuse unusual ABI into main doc Jonathan Cameron
2022-06-26 22:37 ` Mauro Carvalho Chehab
2022-06-27 14:09 ` Jonathan Cameron
2022-06-28 5:51 ` Mauro Carvalho Chehab
2022-07-18 17:39 ` Jonathan Cameron
2022-06-26 16:55 ` [PATCH 4/4] iio: ABI: sx9324: Squash some formatting to keep scripting happy Jonathan Cameron
2022-06-26 22:44 ` Mauro Carvalho Chehab
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=20220626233331.2e8e38d1@sal.lan \
--to=mchehab@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=navin@linumiz.com \
--cc=paresh.chaudhary@rockwellcollins.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