From: Cristian Pop <cristian.pop@analog.com>
To: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <jic23@kernel.org>, Cristian Pop <cristian.pop@analog.com>
Subject: [PATCH v6 2/4] iio:Documentation: Add documentation for label channel attribute
Date: Mon, 21 Sep 2020 16:30:18 +0300 [thread overview]
Message-ID: <20200921133020.62978-2-cristian.pop@analog.com> (raw)
In-Reply-To: <20200921133020.62978-1-cristian.pop@analog.com>
If a label is defined for this channel add that to the channel specific
attributes. This is useful for userspace to be able to identify an
individual channel.
Signed-off-by: Cristian Pop <cristian.pop@analog.com>
---
Changes in v6:
- Fix documentation
Documentation/ABI/testing/sysfs-bus-iio | 72 +++++++++++++++++++++++++
1 file changed, 72 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
index a9d51810a3ba..53c5156362af 100644
--- a/Documentation/ABI/testing/sysfs-bus-iio
+++ b/Documentation/ABI/testing/sysfs-bus-iio
@@ -1715,6 +1715,78 @@ Description:
Raw counter device counters direction for channel Y.
+What: /sys/bus/iio/devices/iio:deviceX/in_voltageY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_voltageY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_currentY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_currentY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_powerY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_powerY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_accelY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_accelY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_angl_velY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_angl_velY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_magnY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_magnY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_lightY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_lightY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_intensityY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_intensityY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_proximityY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_proximityY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_tempY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_tempY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_incliY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_incliY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_rotY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_rotY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_anglY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_anglY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_timestampY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_timestampY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_capacitanceY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_capacitanceY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_altvoltageY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_altvoltageY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_cctY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_cctY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_pressureY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_pressureY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_humidityrelativeY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_humidityrelativeY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_activityY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_activityY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_stepsY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_stepsY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_energyY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_energyY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_distanceY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_distanceY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_velocityY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_velocityY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_concentrationY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_concentrationY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_resistanceY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_resistanceY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_phY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_phY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_uvindexY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_uvindexY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_electricalconductivityY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_electricalconductivityY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_countY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_countY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_indexY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_indexY_label
+What: /sys/bus/iio/devices/iio:deviceX/in_gravityY_label
+What: /sys/bus/iio/devices/iio:deviceX/out_gravityY_label
+KernelVersion: 5.8
+Contact: linux-iio@vger.kernel.org
+Description:
+ Optional symbolic label to a device channel.
+ If a label is defined for this channel add that to the channel
+ specific attributes. This is useful for userspace to be able to
+ better identify an individual channel.
+
What: /sys/bus/iio/devices/iio:deviceX/in_phaseY_raw
KernelVersion: 4.18
Contact: linux-iio@vger.kernel.org
--
2.17.1
next prev parent reply other threads:[~2020-09-21 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 13:30 [PATCH v6 1/4] iio: core: Add optional symbolic label to a device channel Cristian Pop
2020-09-21 13:30 ` Cristian Pop [this message]
2020-09-25 12:12 ` [PATCH v6 2/4] iio:Documentation: Add documentation for label channel attribute Jonathan Cameron
2020-09-21 13:30 ` [PATCH v6 3/4] iio: adc: ad7768-1: Add channel labels Cristian Pop
2020-09-21 13:30 ` [PATCH v6 4/4] dt-bindings:iio:adc:adi,ad7768-1: Add documentation for channel label Cristian Pop
2020-09-25 12:04 ` Jonathan Cameron
2020-09-25 12:13 ` [PATCH v6 1/4] iio: core: Add optional symbolic label to a device channel 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=20200921133020.62978-2-cristian.pop@analog.com \
--to=cristian.pop@analog.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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).