From: sashiko-bot@kernel.org
To: "ShiTou Hong" <redstone.dcity@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/6] arm64: dts: qcom: sm8250-hdk: Enable the sdhc_2 port
Date: Thu, 22 Oct 2026 11:49:51 +0000 [thread overview]
Message-ID: <sashiko-outbox-181397@kernel.org> (raw)
In-Reply-To: <20261022113601.2320940-1-dc_redstone@outlook.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] arm64: dts: qcom: sm8250-hdk: sd-ufs-cd-pins violates TLMM DT binding schema
--
commit 0b99efa9e9916abab14b14dc1f0beae18f4f1e7f
Author: redstonee <1516235445@qq.com>
arm64: dts: qcom: sm8250-hdk: Enable the sdhc_2 port
This patch adds the default pin configuration state for sdc2 in sm8250.dtsi
and enables the sdhc_2 controller along with its card-detect pin
configuration on the sm8250-hdk board.
> diff --git a/arch/arm64/boot/dts/qcom/sm8250-hdk.dts b/arch/arm64/boot/dts/qcom/sm8250-hdk.dts
> index c1c673086df51..5975878ea0fd2 100644
> --- a/arch/arm64/boot/dts/qcom/sm8250-hdk.dts
> +++ b/arch/arm64/boot/dts/qcom/sm8250-hdk.dts
> @@ -398,6 +398,12 @@ &qupv3_id_1 {
>
> &tlmm {
> gpio-reserved-ranges = <28 4>, <40 4>;
> +
> + sd_ufs_cd_pins: sd-ufs-cd-pins {
> + pins = "gpio77";
> + function = "gpio";
> + bias-pull-up;
> + };
> };
[Severity: Low]
Does naming this direct child node of &tlmm sd-ufs-cd-pins cause a dtbs_check
schema validation regression?
In Documentation/devicetree/bindings/pinctrl/qcom,sm8250-pinctrl.yaml,
direct child pin configuration nodes under the tlmm controller must match
the "-state$" pattern (with "-pins$" only allowed for subnodes nested inside
a "-state" node):
patternProperties:
"-state$":
oneOf:
- $ref: "#/$defs/qcom-sm8250-tlmm-state"
- patternProperties:
"-pins$":
$ref: "#/$defs/qcom-sm8250-tlmm-state"
additionalProperties: false
Should this node be named with a -state suffix (for example,
sd-ufs-cd-state) to match the binding schema?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261022113601.2320940-1-dc_redstone@outlook.com?part=1
next prev parent reply other threads:[~2026-10-22 11:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-22 11:35 [PATCH 1/6] arm64: dts: qcom: sm8250-hdk: Enable the sdhc_2 port ShiTou Hong
2026-10-22 11:35 ` [PATCH 2/6] arm64: dts: qcom: sm8250-hdk: Add LT9611UXC HDMI bridge ShiTou Hong
2026-10-22 11:53 ` sashiko-bot
2026-10-22 11:35 ` [PATCH 3/6] arm64: dts: qcom: sm8250-hdk: Add FSA4480 USB-C protocol chip ShiTou Hong
2026-10-22 11:35 ` [PATCH 4/6] arm64: dts: qcom: sm8250-hdk: Enable the PCIe ports ShiTou Hong
2026-10-22 11:46 ` sashiko-bot
2026-10-22 11:36 ` [PATCH 5/6] arm64: dts: qcom: sm8250-hdk: Add the QCA6390 NIC ShiTou Hong
2026-10-22 11:52 ` sashiko-bot
2026-10-22 11:36 ` [PATCH 6/6] arm64: dts: qcom: sm8250-hdk: Add the 2 LEDs of PM8150b ShiTou Hong
2026-10-22 11:42 ` sashiko-bot
2026-10-22 11:49 ` sashiko-bot [this message]
2026-10-22 11:56 ` [PATCH 1/6] arm64: dts: qcom: sm8250-hdk: Enable the sdhc_2 port Konrad Dybcio
-- strict thread matches above, loose matches on Subject: below --
2026-10-23 7:28 ShiTou Hong
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-181397@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=redstone.dcity@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