devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Joshua Felmeden <jfelmeden@thegoodpenguin.co.uk>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: humidity: add ENS21x sensor family
Date: Sat, 13 Jul 2024 12:14:42 +0100	[thread overview]
Message-ID: <20240713121442.0fa8ed2c@jic23-huawei> (raw)
In-Reply-To: <20240710-ens21x-v3-1-4e3fbcf2a7fb@thegoodpenguin.co.uk>

On Wed, 10 Jul 2024 14:24:04 +0100
Joshua Felmeden <jfelmeden@thegoodpenguin.co.uk> wrote:

> Add device tree documentation for ENS21x family of temperature and
> humidity sensors
> 
> Signed-off-by: Joshua Felmeden <jfelmeden@thegoodpenguin.co.uk>
> ---
>  .../bindings/iio/humidity/sciosense,ens21x.yaml    | 55 ++++++++++++++++++++++
>  1 file changed, 55 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/iio/humidity/sciosense,ens21x.yaml b/Documentation/devicetree/bindings/iio/humidity/sciosense,ens21x.yaml
> new file mode 100644
> index 000000000000..425d3b57f701
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/humidity/sciosense,ens21x.yaml
> @@ -0,0 +1,55 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/humidity/sciosense,ens21x.yaml#

Normally we don't allow wild cares in binding names, but in this case the
datasheet uses this wild cards, so I guess we have strong guarantees
the manufacturer won't slip something else in the gaps.

Even with that in mind I'd rather this was sciosense,ens210.yaml

As much as anything as to not provide more precedence for wild cards in binding
names that might lead people astray when they don't have such strong guarantees.

Otherwise looks fine to me.

Jonathan


> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: ScioSense ENS21x temperature and humidity sensor
> +
> +maintainers:
> +  - Joshua Felmeden <jfelmeden@thegoodpenguin.co.uk>
> +
> +description: |
> +  Temperature and Humidity sensor.
> +
> +  Datasheet:
> +    https://www.sciosense.com/wp-content/uploads/2024/04/ENS21x-Datasheet.pdf
> +    https://www.sciosense.com/wp-content/uploads/2023/12/ENS210-Datasheet.pdf
> +
> +properties:
> +  compatible:
> +    oneOf:
> +      - items:
> +          - enum:
> +              - sciosense,ens210a
> +              - sciosense,ens211
> +              - sciosense,ens212
> +              - sciosense,ens213a
> +              - sciosense,ens215
> +          - const: sciosense,ens210
> +      - const: sciosense,ens210
> +
> +  reg:
> +    maxItems: 1
> +
> +  vdd-supply: true
> +
> +required:
> +  - compatible
> +  - reg
> +
> +additionalProperties: false
> +
> +examples:
> +  - |
> +    i2c {
> +       #address-cells = <1>;
> +       #size-cells = <0>;
> +
> +       temperature-sensor@43 {
> +           compatible = "sciosense,ens210";
> +           reg = <0x43>;
> +       };
> +    };
> +...
> +
> 


  parent reply	other threads:[~2024-07-13 11:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10 13:24 [PATCH v3 0/2] iio: humidity: Add support for en21x sensor family Joshua Felmeden
2024-07-10 13:24 ` [PATCH v3 1/2] dt-bindings: iio: humidity: add ENS21x " Joshua Felmeden
2024-07-11 21:16   ` Rob Herring (Arm)
2024-07-13 11:14   ` Jonathan Cameron [this message]
2024-07-10 13:24 ` [PATCH v3 2/2] iio: humidity: Add support for ENS21x Joshua Felmeden
2024-07-12 11:50   ` kernel test robot
2024-07-13  7:42   ` kernel test robot
2024-07-13 10:44   ` Christophe JAILLET
2024-07-13 11:47   ` 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=20240713121442.0fa8ed2c@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jfelmeden@thegoodpenguin.co.uk \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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).