From: sashiko-bot@kernel.org
To: "Luiz Angelo Daros de Luca" <luizluca@gmail.com>
Cc: linux-hwmon@vger.kernel.org, robh@kernel.org,
conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [hwmon-next PATCH v6 1/4] dt-bindings: hwmon: add adi,adt7470
Date: Wed, 05 Aug 2026 13:20:51 +0000 [thread overview]
Message-ID: <20260805132052.009341F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260805-adt7470_thermalzone-v6-1-5605a5f95467@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `#pwm-cells` property is defined but omitted from the `required` list in the device tree binding, violating subsystem guidelines for hardware with provider capabilities.
--
--- Patch [1]: [hwmon-next PATCH v6 1/4] dt-bindings: hwmon: add adi,adt7470 ---
commit fe49a8bb78dd4a0eaf6f5fcfe3003d9e2f0f9049
Author: Luiz Angelo Daros de Luca <luizluca@gmail.com>
dt-bindings: hwmon: add adi,adt7470
This commit adds the device tree binding documentation for the Analog Devices
ADT7470 multichannel temperature sensor and PWM fan controller. It defines
support for the thermal framework and models fan control lines as PWM
channels.
> diff --git a/Documentation/devicetree/bindings/hwmon/adi,adt7470.yaml b/Documentation/devicetree/bindings/hwmon/adi,adt7470.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/adi,adt7470.yaml
[ ... ]
> +properties:
> + compatible:
> + const: adi,adt7470
> +
> + reg:
> + maxItems: 1
> +
> + "#pwm-cells":
> + const: 3
> +
> + "#thermal-sensor-cells":
> + const: 1
> + description:
> + Valid index values are 0 to 9, corresponding to temp1 through temp10.
> +
> +required:
> + - compatible
> + - reg
[Severity: Medium]
Should "#pwm-cells" be included in this required list?
When a hardware variant has provider capabilities like a PWM output, the
corresponding properties are typically expected to be present in the required
list. Without it, incomplete device tree nodes lacking the "#pwm-cells"
property might pass schema validation but fail at runtime when dependent
subsystems attempt to use the device as a PWM provider.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260805-adt7470_thermalzone-v6-0-5605a5f95467@gmail.com?part=1
next prev parent reply other threads:[~2026-08-05 13:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 13:15 [hwmon-next PATCH v6 0/4] hwmon: (adt7470) Add PWM provider and thermal sensor support Luiz Angelo Daros de Luca
2026-08-05 13:15 ` [hwmon-next PATCH v6 1/4] dt-bindings: hwmon: add adi,adt7470 Luiz Angelo Daros de Luca
2026-08-05 13:20 ` sashiko-bot [this message]
2026-08-05 14:57 ` Guenter Roeck
2026-08-05 13:15 ` [hwmon-next PATCH v6 2/4] hwmon: (adt7470) Add ADT7470_PWM_MAX macro Luiz Angelo Daros de Luca
2026-08-05 13:30 ` sashiko-bot
2026-08-05 14:58 ` Guenter Roeck
2026-08-05 13:15 ` [hwmon-next PATCH v6 3/4] hwmon: (adt7470) Expose fan control via PWM framework Luiz Angelo Daros de Luca
2026-08-05 13:33 ` sashiko-bot
2026-08-05 14:58 ` Guenter Roeck
2026-08-05 13:15 ` [hwmon-next PATCH v6 4/4] hwmon: (adt7470) Add thermal zone sensor support Luiz Angelo Daros de Luca
2026-08-05 13:30 ` sashiko-bot
2026-08-05 15:01 ` Guenter Roeck
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=20260805132052.009341F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=luizluca@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