From: Jonathan Cameron <jic23@kernel.org>
To: Anshul Dalal <anshulusr@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH v4 2/3] dt-bindings: iio: chemical: add aosong,ags02ma
Date: Sat, 25 Nov 2023 12:12:45 +0000 [thread overview]
Message-ID: <20231125121245.6664470d@jic23-huawei> (raw)
In-Reply-To: <20231125100139.193584-2-anshulusr@gmail.com>
On Sat, 25 Nov 2023 15:31:37 +0530
Anshul Dalal <anshulusr@gmail.com> wrote:
> Add bindings for Aosong AGS02MA TVOC sensor.
>
> The sensor communicates over i2c with the default address 0x1a.
> TVOC values can be read in the units of ppb and ug/m^3 at register 0x00.
>
> Datasheet:
> https://asairsensors.com/wp-content/uploads/2021/09/AGS02MA.pdf
> Product-Page:
> http://www.aosong.com/m/en/products-33.html
>
> Signed-off-by: Anshul Dalal <anshulusr@gmail.com>
> ---
>
> Changes for v4:
> - Changed node name from 'light-sensor' to 'voc-sensor'
>
> v3: https://lore.kernel.org/lkml/20231121095800.2180870-2-anshulusr@gmail.com/
>
> Changes for v3:
> - Fixed commit message
> - Removed "asair,ags02ma" compatible
>
> v2: https://lore.kernel.org/lkml/20231115125810.1394854-2-anshulusr@gmail.com/
>
> Changes for v2:
> - Removed device from trivial-devices
> - Added standalone binding with vdd-supply property
>
> v1: https://lore.kernel.org/lkml/20231107173100.62715-2-anshulusr@gmail.com/
> ---
> .../bindings/iio/chemical/aosong,ags02ma.yaml | 46 +++++++++++++++++++
> 1 file changed, 46 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/iio/chemical/aosong,ags02ma.yaml
>
> diff --git a/Documentation/devicetree/bindings/iio/chemical/aosong,ags02ma.yaml b/Documentation/devicetree/bindings/iio/chemical/aosong,ags02ma.yaml
> new file mode 100644
> index 000000000000..c176a6e102ac
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/chemical/aosong,ags02ma.yaml
> @@ -0,0 +1,46 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/chemical/aosong,ags02ma.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Aosong AGS02MA VOC Sensor
> +
> +description: |
> + AGS02MA is an TVOC (Total Volatile Organic Compounds) i2c sensor with default
> + address of 0x1a.
> +
> + Datasheet:
> + https://asairsensors.com/wp-content/uploads/2021/09/AGS02MA.pdf
> +
> +maintainers:
> + - Anshul Dalal <anshulusr@gmail.com>
> +
> +properties:
> + compatible:
> + enum:
> + - aosong,ags02ma
> +
> + reg:
> + maxItems: 1
> +
> + vdd-supply: true
Similar to other review (I put more background there)
Convention these days at least is to always require powersupplies
that the device cannot work with out (even if you can use a fixed
supply and rely on the regulator framework papering over that).
We want to distinguish generally optional supplies from ones we might
not specify in a given DT.
Jonathan
> +
> +required:
> + - compatible
> + - reg
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + voc-sensor@1a {
> + compatible = "aosong,ags02ma";
> + reg = <0x1a>;
> + vdd-supply = <&vdd_regulator>;
> + };
> + };
next prev parent reply other threads:[~2023-11-25 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-25 10:01 [PATCH v4 1/3] dt-bindings: vendor-prefixes: add aosong Anshul Dalal
2023-11-25 10:01 ` [PATCH v4 2/3] dt-bindings: iio: chemical: add aosong,ags02ma Anshul Dalal
2023-11-25 10:36 ` Krzysztof Kozlowski
2023-11-25 12:12 ` Jonathan Cameron [this message]
2023-11-25 10:01 ` [PATCH v4 3/3] iio: chemical: add support for Aosong AGS02MA Anshul Dalal
2023-11-25 12:26 ` Jonathan Cameron
2023-11-25 10:35 ` [PATCH v4 1/3] dt-bindings: vendor-prefixes: add aosong Krzysztof Kozlowski
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=20231125121245.6664470d@jic23-huawei \
--to=jic23@kernel.org \
--cc=anshulusr@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.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