linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cristian Pop <cristian.pop@analog.com>
To: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <jic23@kernel.org>, <devicetree@vger.kernel.org>,
	<robh+dt@kernel.org>, Cristian Pop <cristian.pop@analog.com>
Subject: [PATCH v7 5/5] dt-bindings:iio:adc:adc.txt: Add documentation for channel label attribute
Date: Mon, 2 Nov 2020 16:20:00 +0200	[thread overview]
Message-ID: <20201102142000.68916-5-cristian.pop@analog.com> (raw)
In-Reply-To: <20201102142000.68916-1-cristian.pop@analog.com>

Optional attribute for better identification of the channels.

Signed-off-by: Cristian Pop <cristian.pop@analog.com>
---
Changes in v7:
 - Add this extra commit
 Documentation/devicetree/bindings/iio/adc/adc.txt | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation/devicetree/bindings/iio/adc/adc.txt b/Documentation/devicetree/bindings/iio/adc/adc.txt
index 5bbaa330a250..4b37575bbddc 100644
--- a/Documentation/devicetree/bindings/iio/adc/adc.txt
+++ b/Documentation/devicetree/bindings/iio/adc/adc.txt
@@ -5,18 +5,24 @@ Optional properties for child nodes:
 - diff-channels : Differential channels muxed for this ADC. The first value
 		specifies the positive input pin, the second value the negative
 		input pin.
+- reg: The channel number.
+- label: Unique name to identify which channel this is.
 
 Example:
 	adc@0 {
 		compatible = "some,adc";
 		...
 		channel@0 {
+			reg = <0>;
+			label = "channel_0_name";
 			bipolar;
 			diff-channels = <0 1>;
 			...
 		};
 
 		channel@1 {
+			reg = <1>;
+			label = "channel_1_name";
 			diff-channels = <2 3>;
 			...
 		};
-- 
2.17.1


  parent reply	other threads:[~2020-11-02 14:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-02 14:19 [PATCH v7 1/5] iio: core: Add optional symbolic label to a device channel Cristian Pop
2020-11-02 14:19 ` [PATCH v7 2/5] iio:Documentation: Add documentation for label channel attribute Cristian Pop
2020-11-02 14:19 ` [PATCH v7 3/5] iio: adc: ad7768-1: Add channel labels Cristian Pop
2020-11-02 14:19 ` [PATCH v7 4/5] dt-bindings:iio:adc:adi,ad7768-1: Add documentation for channel label Cristian Pop
2020-11-05 17:19   ` Rob Herring
2020-11-02 14:20 ` Cristian Pop [this message]
2020-11-05 17:37   ` [PATCH v7 5/5] dt-bindings:iio:adc:adc.txt: Add documentation for channel label attribute Rob Herring
2020-11-08 15:29     ` Jonathan Cameron
  -- strict thread matches above, loose matches on Subject: below --
2020-11-02 14:16 [PATCH v7 1/5] iio: core: Add optional symbolic label to a device channel Cristian Pop
2020-11-02 14:16 ` [PATCH v7 5/5] dt-bindings:iio:adc:adc.txt: Add documentation for channel label attribute Cristian Pop
2020-09-28  9:09 [PATCH v7 1/5] iio: core: Add optional symbolic label to a device channel Cristian Pop
2020-09-28  9:09 ` [PATCH v7 5/5] dt-bindings:iio:adc:adc.txt: Add documentation for channel label attribute Cristian Pop
2020-09-29 15:48   ` 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=20201102142000.68916-5-cristian.pop@analog.com \
    --to=cristian.pop@analog.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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).