From: Jonathan Cameron <jic23@kernel.org>
To: ruantu <mtwget@gmail.com>
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: iio: chemical: Add bindings for Dynament Premier series single gas sensor
Date: Sun, 15 Dec 2019 17:19:49 +0000 [thread overview]
Message-ID: <20191215171949.1b817a40@archlinux> (raw)
In-Reply-To: <20191210053744.732093-1-mtwget@gmail.com>
On Tue, 10 Dec 2019 13:37:44 +0800
ruantu <mtwget@gmail.com> wrote:
> Dynament Premier series single gas sensor.
>
> Signed-off-by: ruantu <mtwget@gmail.com>
> ---
> .../iio/chemical/dynament,premier.yaml | 43 +++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> MAINTAINERS | 1 +
> 3 files changed, 46 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/chemical/dynament,premier.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/chemical/dynament,premier.yaml b/Documentation/devicetree/bindings/iio/chemical/dynament,premier.yaml
> new file mode 100644
> index 000000000000..076ae9d90cee
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/chemical/dynament,premier.yaml
> @@ -0,0 +1,43 @@
> +# SPDX-License-Identifier: GPL-2.0
The dt maintainers are asking if possible for all new bindings to be dual licensed
with BSD as it makes them easier to reuse outside linux.
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/chemical/dynament,premier.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Dynament Premier series single gas sensor
> +
> +maintainers:
> + - ruantu <mtwget@gmail.com>
> +
> +description: |
> + single gas sensor capable of measuring gas concentration of dust
> + particles, multi-gas sensor are not supported.
> +
> + Specifications about the sensor can be found at:
> + https://www.dynament.com/_webedit/uploaded-files/All%20Files/SIL%20Data/tds0045_1.44.pdf, read chapter 1.5.2 Read live data simple
> +
> +properties:
> + compatible:
> + enum:
> + - dynament,premier
> +
> + vcc-supply:
> + description: regulator that provides power to the sensor
> +
> + reset-gpios:
> + description: GPIO connected to the RESET line
> + maxItems: 1
Good to have the regulator and reset defined from the start. It may be worth adding
the regulator enable to the driver. Reset is actually optional I assume whereas
power isn't (it's just a question of whether it is already turned on or not!)
> +
> +required:
> + - compatible
> +
> +examples:
> + - |
> + serial {
> + single-gas-sensor {
> + compatible = "dynament,premier";
> + vcc-supply = <®_vcc5v0>;
> + };
> + };
Bindings have indented in multiples of 4 spaces I believe. That needs tidying
up in this example.
Thanks,
Jonathan
> +
> +...
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> index 6046f4555852..5afca0586c41 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
> @@ -261,6 +261,8 @@ patternProperties:
> description: Dragino Technology Co., Limited
> "^dserve,.*":
> description: dServe Technology B.V.
> + "^dynament,.*":
> + description: Dynament, Ltd.
> "^ea,.*":
> description: Embedded Artists AB
> "^ebs-systart,.*":
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 18c26558ddfe..84592789e01b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -13137,6 +13137,7 @@ DYNAMENT PREMIER SERIES SINGLE GAS SENSOR DRIVER
> M: ruantu <mtwget@gmail.com>
> S: Maintained
> F: drivers/iio/chemical/premier.c
> +F: Documentation/devicetree/bindings/iio/chemical/dynament,premier.yaml
>
> PLANTOWER PMS7003 AIR POLLUTION SENSOR DRIVER
> M: Tomasz Duszynski <tduszyns@gmail.com>
prev parent reply other threads:[~2019-12-15 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 5:37 [PATCH 2/2] dt-bindings: iio: chemical: Add bindings for Dynament Premier series single gas sensor ruantu
2019-12-15 17:19 ` 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=20191215171949.1b817a40@archlinux \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtwget@gmail.com \
--cc=pmeerw@pmeerw.net \
/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