linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Zaikonnikov <ez@norphonic.com>
To: Rob Herring <robh+dt@kernel.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
	development@norphonic.com, Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio <linux-iio@vger.kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Subject: [PATCH v9 2/2] dt-bindings: iio: humidity: Add TI HDC20x0 support
Date: Fri, 10 Jul 2020 14:20:58 +0200	[thread overview]
Message-ID: <86blknd0id.fsf@norphonic.com> (raw)
In-Reply-To: <86d053d1re.fsf@norphonic.com>

[-- Attachment #1: Type: text/plain, Size: 231 bytes --]

Add device tree bindings for HDC2010/HDC2080 family of humidity and
temperature sensors.

Changes from v8:
- document the use of reg
- change the license terms to GPL-2.0-only

Signed-off-by: Eugene Zaikonnikov <ez@norphonic.com>


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: iio-hdc2010-driver-docs.patch --]
[-- Type: text/x-diff, Size: 1316 bytes --]

diff -uprN linux-5.3.8/Documentation/devicetree/bindings/iio/humidity/ti,hdc2010.yaml linux-5.3.8_docs/Documentation/devicetree/bindings/iio/humidity/ti,hdc2010.yaml
--- linux-5.3.8/Documentation/devicetree/bindings/iio/humidity/ti,hdc2010.yaml	1970-01-01 01:00:00.000000000 +0100
+++ linux-5.3.8_docs/Documentation/devicetree/bindings/iio/humidity/ti,hdc2010.yaml	2020-07-10 13:08:46.818076734 +0200
@@ -0,0 +1,45 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/iio/humidity/ti,hdc2010.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: HDC2010/HDC2080 humidity and temperature iio sensors
+
+maintainers:
+  - Eugene Zaikonnikov <ez@norophonic.com>
+
+description: |
+  Relative humidity and tempereature sensors on I2C bus
+
+  Datasheets are available at:
+    http://www.ti.com/product/HDC2010/datasheet
+    http://www.ti.com/product/HDC2080/datasheet
+
+properties:
+  compatible:
+    enum:
+      - ti,hdc2010
+      - ti,hdc2080
+
+  vdd-supply:
+    maxItems: 1
+
+  reg:
+    maxItems: 1
+
+required:
+  - compatible
+  - reg
+
+examples:
+  - |
+    i2c0 {
+      #address-cells = <1>;
+      #size-cells = <0>;
+
+      humidity@40 {
+          compatible = "ti,hdc2010";
+          reg = <0x40>;
+      };
+    };

  reply	other threads:[~2020-07-10 12:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 11:53 [PATCH v9 1/2] iio: humidity: Add TI HDC20x0 support Eugene Zaikonnikov
2020-07-10 12:20 ` Eugene Zaikonnikov [this message]
2020-07-12 10:59   ` [PATCH v9 2/2] dt-bindings: " Jonathan Cameron
2020-07-13 15:38     ` Rob Herring
2020-07-11 15:16 ` [PATCH v9 1/2] " Andy Shevchenko
2020-07-11 15:27 ` Andy Shevchenko
2020-07-12 10:54   ` Jonathan Cameron
2020-08-04 10:23     ` Eugene Zaikonnikov
2020-08-06 18:46       ` Jonathan Cameron
2020-08-07  7:28         ` Eugene Zaikonnikov
2020-08-03 14:43   ` Eugene Zaikonnikov
2020-08-03 16:37     ` Andy Shevchenko

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=86blknd0id.fsf@norphonic.com \
    --to=ez@norphonic.com \
    --cc=development@norphonic.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --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).