From: Paul Cercueil <paul@crapouillou.net>
To: "Jonathan Cameron" <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Guido Günther" <agx@sigxcpu.org>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Paul Cercueil <paul@crapouillou.net>
Subject: [PATCH] dt-bindings: iio: Document "label" property
Date: Tue, 21 Dec 2021 10:43:54 +0000 [thread overview]
Message-ID: <20211221104354.35073-1-paul@crapouillou.net> (raw)
All iio devices can have a label, which will be carried on to userspace
as a sysfs attribute. This is useful when having several iio devices
that represent different instances of the same hardware, as the name
attribute would then not be enough to differentiate between them.
Signed-off-by: Paul Cercueil <paul@crapouillou.net>
---
Documentation/devicetree/bindings/iio/common.yaml | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/bindings/iio/common.yaml b/Documentation/devicetree/bindings/iio/common.yaml
index f845b41d74c4..a90ad7718ecf 100644
--- a/Documentation/devicetree/bindings/iio/common.yaml
+++ b/Documentation/devicetree/bindings/iio/common.yaml
@@ -32,6 +32,14 @@ properties:
considered 'near' to the device (an object is near to the
sensor).
+ label:
+ $ref: /schemas/types.yaml#/definitions/string
+ description: |
+ All iio devices can have a label, which will be carried on to userspace
+ as a sysfs attribute. This is useful when having several iio devices that
+ represent different instances of the same hardware, as the name attribute
+ would then not be enough to differentiate between them.
+
additionalProperties: true
...
--
2.34.1
next reply other threads:[~2021-12-21 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 10:43 Paul Cercueil [this message]
2021-12-21 11:29 ` Lars-Peter Clausen
2021-12-21 12:38 ` Paul Cercueil
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=20211221104354.35073-1-paul@crapouillou.net \
--to=paul@crapouillou.net \
--cc=agx@sigxcpu.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--subject='Re: [PATCH] dt-bindings: iio: Document "label" property' \
/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
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.