From: sashiko-bot@kernel.org
To: "Troy Mitchell" <troy.mitchell@linux.dev>
Cc: conor+dt@kernel.org, linux-hwmon@vger.kernel.org,
robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/6] dt-bindings: hwmon: Move LM63 family to a dedicated binding
Date: Tue, 21 Jul 2026 09:58:20 +0000 [thread overview]
Message-ID: <20260721095822.1E9631F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260721-ctl2301-v2-2-ef5fb342872a@linux.dev>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Missing `interrupts` property in the newly created LM63 device tree binding.
--
--- Patch [2]: [PATCH v2 2/6] dt-bindings: hwmon: Move LM63 family to a dedicated binding ---
commit 5cb7233d8984d02f9823102bcec286ee4ef134d5
Author: Troy Mitchell <troy.mitchell@linux.dev>
dt-bindings: hwmon: Move LM63 family to a dedicated binding
This commit moves the National Semiconductor LM63, LM64, and LM96163
compatibles out of trivial-devices.yaml and into a dedicated schema. It also
describes their integrated fan control and thermal cooling device capabilities.
> diff --git a/Documentation/devicetree/bindings/hwmon/national,lm63.yaml b/Documentation/devicetree/bindings/hwmon/national,lm63.yaml
> new file mode 100644
> index 0000000000000..92b0094ff3034
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/hwmon/national,lm63.yaml
[ ... ]
> +properties:
> + compatible:
> + enum:
> + - national,lm63
> + - national,lm64
> + - national,lm96163
> +
> + reg:
> + maxItems: 1
> +
> + "#cooling-cells":
> + const: 2
[Severity: Medium]
Should the interrupts property be explicitly defined in this block?
Because the LM63 family was moved out of trivial-devices.yaml (which broadly
permitted the interrupts property) to a dedicated schema using
unevaluatedProperties: false, device trees that correctly describe the
hardware's interrupt capability via the ALERT# pin will now incorrectly fail
dtbs_check validation.
> +
> +required:
> + - compatible
> + - reg
> +
> +unevaluatedProperties: false
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260721-ctl2301-v2-0-ef5fb342872a@linux.dev?part=2
next prev parent reply other threads:[~2026-07-21 9:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 9:48 [PATCH v2 0/6] hwmon: (lm63) Add Sensylink CTF2301 support Troy Mitchell
2026-07-21 9:48 ` [PATCH v2 1/6] dt-bindings: vendor-prefixes: Add Sensylink Troy Mitchell
2026-07-21 9:51 ` sashiko-bot
2026-07-21 15:49 ` Conor Dooley
2026-07-21 17:56 ` Guenter Roeck
2026-07-21 9:48 ` [PATCH v2 2/6] dt-bindings: hwmon: Move LM63 family to a dedicated binding Troy Mitchell
2026-07-21 9:58 ` sashiko-bot [this message]
2026-07-21 11:38 ` Troy Mitchell
2026-07-21 9:48 ` [PATCH v2 3/6] dt-bindings: hwmon: Add Sensylink CTF2301 Troy Mitchell
2026-07-21 9:57 ` sashiko-bot
2026-07-21 15:46 ` Conor Dooley
2026-07-21 9:48 ` [PATCH v2 4/6] hwmon: (lm63) Add Sensylink CTF2301 support Troy Mitchell
2026-07-21 10:00 ` sashiko-bot
2026-07-21 11:52 ` Troy Mitchell
2026-07-21 9:48 ` [PATCH v2 5/6] riscv: dts: spacemit: Add K3 I2C6 pinctrl state Troy Mitchell
2026-07-21 10:00 ` sashiko-bot
2026-07-21 11:52 ` Troy Mitchell
2026-07-21 9:48 ` [PATCH v2 6/6] riscv: dts: spacemit: Add CTF2301 on K3 CoM260 Troy Mitchell
2026-07-21 10:00 ` sashiko-bot
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=20260721095822.1E9631F000E9@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=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=troy.mitchell@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