devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: lorenzo.bianconi@redhat.com, devicetree@vger.kernel.org,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: iio: humidity: hts221: introduce vdd regulator bindings
Date: Sat, 21 Nov 2020 15:45:23 +0000	[thread overview]
Message-ID: <20201121154523.0c0421b6@archlinux> (raw)
In-Reply-To: <5e8009b293f1d5160ecbcdd33e7332ba0192b96e.1605777052.git.lorenzo@kernel.org>

On Thu, 19 Nov 2020 10:13:35 +0100
Lorenzo Bianconi <lorenzo@kernel.org> wrote:

> Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
I'd drop the description as kind of obvious.

vdd-supply: true

will work fine.

Thanks,

Jonathan

> ---
>  Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml b/Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml
> index 396451c26728..53df083b3de6 100644
> --- a/Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml
> +++ b/Documentation/devicetree/bindings/iio/humidity/st,hts221.yaml
> @@ -26,6 +26,9 @@ properties:
>        The interrupt/data ready line will be configured as open drain, which
>        is useful if several sensors share the same interrupt line.
>  
> +  vdd-supply:
> +    description: if defined provides VDD power to the sensor.
> +
>    interrupts:
>      maxItems: 1
>  


      reply	other threads:[~2020-11-21 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19  9:13 [PATCH 0/2] hts221: add vdd power regulator Lorenzo Bianconi
2020-11-19  9:13 ` [PATCH 1/2] iio: humidity: hts221: add vdd voltage regulator Lorenzo Bianconi
2020-11-21 15:44   ` Jonathan Cameron
2020-11-19  9:13 ` [PATCH 2/2] dt-bindings: iio: humidity: hts221: introduce vdd regulator bindings Lorenzo Bianconi
2020-11-21 15:45   ` Jonathan Cameron [this message]

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=20201121154523.0c0421b6@archlinux \
    --to=jic23@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=lorenzo@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).