From: sashiko-bot@kernel.org
To: "Sachin Gupta" <sachin.gupta@oss.qualcomm.com>
Cc: mfd@lists.linux.dev, lee@kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: thermal: Add Qualcomm MBG thermal monitor support
Date: Wed, 22 Jul 2026 10:54:57 +0000 [thread overview]
Message-ID: <20260722105457.927B21F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260722-spmi-mbg-driver-v3-1-ef73064f2789@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The generic `^temperature-sensor@[0-9a-f]+$` node name pattern in the SPMI PMIC schema is exclusively bound to the `qcom,pm8775-mbg-tm` schema, which causes validation failures for other thermal peripherals (like `qcom,spmi-temp-alarm`) that use the standard `temperature-sensor` generic node name.
--
--- Patch [1]: [PATCH v3 1/2] dt-bindings: thermal: Add Qualcomm MBG thermal monitor support ---
commit 0d6b48e0b8d3e826b0476c17d69e98ce1c6de883
Author: Satya Priya Kakitapalli <quic_skakitap@quicinc.com>
dt-bindings: thermal: Add Qualcomm MBG thermal monitor support
This commit adds device tree bindings for the Qualcomm Master Bandgap (MBG)
temperature alarm peripheral found on the PM8775 PMIC. It supports both hot
and cold threshold monitoring with interrupt status reported over SPMI.
> diff --git a/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml b/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml
> index 809be2756a0c0..bd77cb7173e26 100644
> --- a/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml
> +++ b/Documentation/devicetree/bindings/mfd/qcom,spmi-pmic.yaml
> @@ -194,6 +194,10 @@ patternProperties:
> type: object
> $ref: /schemas/thermal/qcom,spmi-temp-alarm.yaml#
>
> + "^temperature-sensor@[0-9a-f]+$":
> + type: object
> + $ref: /schemas/thermal/qcom,pm8775-mbg-tm.yaml#
[Severity: Medium]
Will this exclusive mapping cause validation failures for other thermal
peripherals?
If a device tree uses a standard temperature-sensor@... node name with a
different compatible string (such as qcom,spmi-temp-alarm) under a
qcom,spmi-pmic node, it seems it would incorrectly fail dtbs_check validation
because it is strictly bound to qcom,pm8775-mbg-tm.yaml here.
Should this pattern property use a oneOf block to permit any supported
thermal sensor schema, rather than binding the generic node name strictly
to the MBG schema?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260722-spmi-mbg-driver-v3-0-ef73064f2789@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-07-22 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 10:44 [PATCH v3 0/2] thermal: qcom: Add Qualcomm SPMI MBG thermal monitor support Sachin Gupta
2026-07-22 10:44 ` [PATCH v3 1/2] dt-bindings: thermal: Add Qualcomm " Sachin Gupta
2026-07-22 10:54 ` sashiko-bot [this message]
2026-07-22 10:44 ` [PATCH v3 2/2] thermal: qcom: Add support for Qualcomm MBG thermal monitoring Sachin Gupta
2026-07-22 10:55 ` 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=20260722105457.927B21F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee@kernel.org \
--cc=mfd@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sachin.gupta@oss.qualcomm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.