From: sashiko-bot@kernel.org
To: "Binbin Zhou" <zhoubinbin@loongson.cn>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, lee@kernel.org,
mfd@lists.linux.dev, robh@kernel.org
Subject: Re: [PATCH v2 2/4] dt-bindings: mfd: syscon: Allow syscon compatible for Loongson-2K0300 chip id
Date: Tue, 21 Jul 2026 12:30:01 +0000 [thread overview]
Message-ID: <20260721123001.889C91F000E9@smtp.kernel.org> (raw)
In-Reply-To: <bab36775095bb85827676b2db917e6cb9527b325.1784619512.git.zhoubinbin@loongson.cn>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The compatible string added in the patch contains a typographical error ('cphipid' instead of 'chipid').
--
--- Patch [2]: [PATCH v2 2/4] dt-bindings: mfd: syscon: Allow syscon compatible for Loongson-2K0300 chip id ---
commit 5db600cb90f648eab2d8d155fce1a1ef7e8cd50e
Author: Binbin Zhou <zhoubinbin@loongson.cn>
dt-bindings: mfd: syscon: Allow syscon compatible for Loongson-2K0300 chip id
The Loongson-2K0300 SoC exposes its chip ID registers through a syscon
interface. This commit adds a specific compatible string to the syscon
bindings list so it can be referenced by a phandle.
> diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml b/Documentation/devicetree/bindings/mfd/syscon.yaml
> index e228670880631..c5b2e28f6cedd 100644
> --- a/Documentation/devicetree/bindings/mfd/syscon.yaml
> +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml
> @@ -76,6 +76,7 @@ select:
> - hpe,gxp-sysreg
> - loongson,ls1b-syscon
> - loongson,ls1c-syscon
> + - loongson,ls2k0300-cphipid-syscon
[Severity: Medium]
Is this spelling correct? The commit message mentions the compatible string
should be "loongson,ls2k0300-chipid-syscon", but this adds "cphipid" instead.
Will this cause schema validation to fail for device trees using the correctly
spelled chipid string?
> - lsi,axxia-syscon
> - marvell,armada-3700-cpu-misc
> - marvell,armada-3700-nb-pm
[ ... ]
> @@ -189,6 +190,7 @@ properties:
> - hpe,gxp-sysreg
> - loongson,ls1b-syscon
> - loongson,ls1c-syscon
> + - loongson,ls2k0300-cphipid-syscon
[Severity: Medium]
Does this also contain the same "cphipid" typo as the select block above?
> - lsi,axxia-syscon
> - marvell,armada-3700-cpu-misc
> - marvell,armada-3700-nb-pm
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1784619512.git.zhoubinbin@loongson.cn?part=2
next prev parent reply other threads:[~2026-07-21 12:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 12:24 [PATCH v2 0/4] thermal: loongson2: Add support for Loongson-2K0300 SoC Binbin Zhou
2026-07-21 12:24 ` [PATCH v2 1/4] thermal/drivers/loongson2: Correct thermal sensor registration loop Binbin Zhou
2026-07-21 12:36 ` sashiko-bot
2026-07-21 12:24 ` [PATCH v2 2/4] dt-bindings: mfd: syscon: Allow syscon compatible for Loongson-2K0300 chip id Binbin Zhou
2026-07-21 12:30 ` sashiko-bot [this message]
2026-07-21 15:39 ` Conor Dooley
2026-07-21 12:26 ` [PATCH v2 3/4] dt-bindings: thermal: loongson,ls2k-thermal: Add compatible for Loongson-2K0300 Binbin Zhou
2026-07-21 12:35 ` sashiko-bot
2026-07-21 15:39 ` Conor Dooley
2026-07-21 12:26 ` [PATCH v2 4/4] thermal/drivers/loongson2: Add support " Binbin Zhou
2026-07-21 12:33 ` 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=20260721123001.889C91F000E9@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=sashiko-reviews@lists.linux.dev \
--cc=zhoubinbin@loongson.cn \
/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