From: Tomasz Duszynski <tomasz.duszynski@octakon.com>
To: <linux-iio@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<jic23@kernel.org>, <lars@metafoo.de>, <robh+dt@kernel.org>,
Tomasz Duszynski <tomasz.duszynski@octakon.com>
Subject: [PATCH v3 3/3] dt-bindings: iio: chemical: sps30: update binding with serial example
Date: Mon, 3 May 2021 08:00:14 +0200 [thread overview]
Message-ID: <20210503060014.7632-4-tomasz.duszynski@octakon.com> (raw)
In-Reply-To: <20210503060014.7632-1-tomasz.duszynski@octakon.com>
sps30 has gained support for serial communication so add example to the
binding file. While at it remove reg property from list of required
properties because it's no-op in case of serial communication.
Signed-off-by: Tomasz Duszynski <tomasz.duszynski@octakon.com>
---
.../devicetree/bindings/iio/chemical/sensirion,sps30.yaml | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/iio/chemical/sensirion,sps30.yaml b/Documentation/devicetree/bindings/iio/chemical/sensirion,sps30.yaml
index a93d1972a5c2..967500b7e773 100644
--- a/Documentation/devicetree/bindings/iio/chemical/sensirion,sps30.yaml
+++ b/Documentation/devicetree/bindings/iio/chemical/sensirion,sps30.yaml
@@ -22,7 +22,6 @@ properties:
required:
- compatible
- - reg
additionalProperties: false
@@ -37,5 +36,11 @@ examples:
reg = <0x69>;
};
};
+ - |
+ serial {
+ air-pollution-sensor {
+ compatible = "sensirion,sps30";
+ };
+ };
...
--
2.31.1
next prev parent reply other threads:[~2021-05-03 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 6:00 [PATCH v3 0/3] iio: sps30: add support for serial interface Tomasz Duszynski
2021-05-03 6:00 ` [PATCH v3 1/3] iio: sps30: separate core and interface specific code Tomasz Duszynski
2021-05-03 6:00 ` [PATCH v3 2/3] iio: sps30: add support for serial interface Tomasz Duszynski
2021-05-03 6:00 ` Tomasz Duszynski [this message]
2021-05-03 10:50 ` [PATCH v3 0/3] " 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=20210503060014.7632-4-tomasz.duszynski@octakon.com \
--to=tomasz.duszynski@octakon.com \
--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 \
/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).