From: Guenter Roeck <linux@roeck-us.net>
To: Chris Ruehl <chris.ruehl@gtsys.com.hk>
Cc: Jack Lo <jack.lo@gtsys.com.hk>,
devicetree@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Rob Herring <robh+dt@kernel.org>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] devicetree: hwmon: shtc1: Add sensirion,shtc1.yaml
Date: Thu, 2 Jul 2020 22:49:54 -0700 [thread overview]
Message-ID: <00c1b143-46c4-2621-bd77-fa465fb77774@roeck-us.net> (raw)
In-Reply-To: <20200703034856.12846-3-chris.ruehl@gtsys.com.hk>
On 7/2/20 8:48 PM, Chris Ruehl wrote:
> Add documentation for the newly added DTS support in the shtc1 driver.
>
> Signed-off-by: Chris Ruehl <chris.ruehl@gtsys.com.hk>
> ---
> .../bindings/hwmon/sensirion,shtc1.yaml | 53 +++++++++++++++++++
> 1 file changed, 53 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/hwmon/sensirion,shtc1.yaml
>
> diff --git a/Documentation/devicetree/bindings/hwmon/sensirion,shtc1.yaml b/Documentation/devicetree/bindings/hwmon/sensirion,shtc1.yaml
> new file mode 100644
> index 000000000000..e3e292bc6d7d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/sensirion,shtc1.yaml
> @@ -0,0 +1,53 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/hwmon/sensirion,shtc1.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Sensirion SHTC1 Humidity and Temperature Sensor IC
> +
> +maintainers:
> + - jdelvare@suse.com
> +
> +description: |
> + The SHTC1, SHTW1 and SHTC3 are digital humidity and temperature sensor
> + designed especially for battery-driven high-volume consumer electronics
> + applications.
> + For further information refere to Documentation/hwmon/shtc1.rst
> +
> + This binding document describes the binding for the hardware monitor
> + portion of the driver.
> +
> +properties:
> + compatible:
> + enum:
> + - sensirion,shtc1
> + - sensirion,shtw1
> + - sensirion,shtc3
> +
> + reg: I2C address 0x70
> +
> +Optional properties:
> + sensirion,blocking_io: |
> + u8, if > 0 the i2c bus hold until measure finished (default 0)
> + sensirion,high_precision: |
> + u8, if > 0 aquire data with high precision (default 1)
> +
Why u8 and not boolean ?
Guenter
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +Example:
> + &i2c1 {
> + status = "okay";
> + clock-frequency = <400000>;
> +
> + shtc3@70 {
> + compatible = "sensirion,shtc3";
> + reg = <0x70>
> + sensirion,blocking_io = <1>;
> + status = "okay";
> + };
> + };
>
next prev parent reply other threads:[~2020-07-03 5:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 3:48 [PATCH] shtc1: add support for device tree bindings Chris Ruehl
2020-07-03 3:48 ` [PATCH 1/2] hwmon: " Chris Ruehl
2020-07-03 5:48 ` Guenter Roeck
2020-07-05 0:34 ` Chris Ruehl
2020-07-03 11:12 ` kernel test robot
2020-07-03 3:48 ` [PATCH 2/2] devicetree: hwmon: shtc1: Add sensirion,shtc1.yaml Chris Ruehl
2020-07-03 5:49 ` Guenter Roeck [this message]
2020-07-05 0:30 ` Chris Ruehl
2020-07-05 2:35 ` Guenter Roeck
2020-07-03 5:35 ` [PATCH] shtc1: add support for device tree bindings Guenter Roeck
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=00c1b143-46c4-2621-bd77-fa465fb77774@roeck-us.net \
--to=linux@roeck-us.net \
--cc=chris.ruehl@gtsys.com.hk \
--cc=devicetree@vger.kernel.org \
--cc=jack.lo@gtsys.com.hk \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@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).