From: sashiko-bot@kernel.org
To: "Akshat Chandra" <notmissinge@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: chemical: Add Sensirion SGP41 binding
Date: Sun, 15 Nov 2026 06:14:33 +0000 [thread overview]
Message-ID: <sashiko-outbox-215241@kernel.org> (raw)
In-Reply-To: <20261115055941.362185-2-notmissinge@gmail.com>
Thank you for your contribution! Sashiko AI review found 3 potential
issues to consider:
- [Medium] dt-bindings: iio: chemical: sgp41: missing vddh-supply for
heater pin
- [Low] dt-bindings: iio: chemical: sgp41: 2-space example indent and
const reg
- [Low] dt-bindings: iio: chemical: sgp41: deprecated GPL-2.0 SPDX
license tag
--
commit 364f23f4f9b681d905ad97232d6cdcac6d5b17e4
Author: Akshat Chandra <notmissinge@gmail.com>
dt-bindings: iio: chemical: Add Sensirion SGP41 binding
This commit adds a Device Tree binding schema for the Sensirion SGP41 VOC
and NOx I2C gas sensor.
> diff --git a/Documentation/devicetree/bindings/iio/chemical/sensirion,sgp41.yaml b/Documentation/devicetree/bindings/iio/chemical/sensirion,sgp41.yaml
> new file mode 100644
> index 0000000000000..c2bb6818f4390
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/chemical/sensirion,sgp41.yaml
> @@ -0,0 +1,43 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
[Severity: Low]
Should this use (GPL-2.0-only OR BSD-2-Clause) instead of the deprecated
GPL-2.0 identifier, per Documentation/devicetree/bindings/submitting-patches.rst?
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/chemical/sensirion,sgp41.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Sensirion SGP41 VOC and NOx gas sensor
> +
> +maintainers:
> + - Akshat Chandra <notmissinge@gmail.com>
> +
> +description: |
> + Sensirion SGP41 indoor air quality sensor measuring raw VOC and NOx
> + signals over I2C.
> +
> +properties:
> + compatible:
> + const: sensirion,sgp41
> +
> + reg:
> + const: 0x59
> +
> + vdd-supply: true
> +
> +required:
> + - compatible
> + - reg
> + - vdd-supply
> +additionalProperties: false
[Severity: Medium]
Should the schema also define vddh-supply?
The SGP41 has a dedicated VDDH pin for the hotplate heater supply in
addition to the logic VDD pin. Boards that power VDD (for example at
1.8 V for I2C) and VDDH from separate regulators cannot describe
vddh-supply in Device Tree when additionalProperties is false without
failing dtbs_check.
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + gas-sensor@59 {
> + compatible = "sensirion,sgp41";
> + reg = <0x59>;
> + vdd-supply = <&vdd>;
> + };
> + };
[Severity: Low]
The example uses 2-space indentation instead of 4 spaces per level, which
triggers an indent-unit-strict warning from scripts/dtc/dt-check-style.
Also, should reg in properties use maxItems: 1 rather than const: 0x59 to
follow standard IIO binding conventions and allow I2C address translation?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261115055941.362185-1-notmissinge@gmail.com?part=1
prev parent reply other threads:[~2026-11-15 6:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261115055941.362185-1-notmissinge@gmail.com>
2026-11-15 5:59 ` [PATCH v2 1/2] dt-bindings: iio: chemical: Add Sensirion SGP41 binding Akshat Chandra
2026-11-15 6:14 ` sashiko-bot [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=sashiko-outbox-215241@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=notmissinge@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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