From: sashiko-bot@kernel.org
To: "Tim Kuo" <Tim.Kuo@mediatek.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: spi: mediatek: add mediatek,spi-ipm-v59 compatible
Date: Thu, 24 Sep 2026 03:19:28 +0000 [thread overview]
Message-ID: <20260924031928.DEEFC1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260924031211.2199921-1-Tim.Kuo@mediatek.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dt-bindings: spi: mediatek: placeholder mediatek,mtxxxx-spi used
--
commit fada8f8666ea668750d2860cbb190b105cbf5cde
Author: Tim Kuo <Tim.Kuo@mediatek.com>
dt-bindings: spi: mediatek: add mediatek,spi-ipm-v59 compatible
This commit adds a new compatible string "mediatek,spi-ipm-v59" for the IPM
v59 SPI IP, as it needs its own fallback compatible rather than reusing the
earlier "mediatek,spi-ipm" design.
> diff --git a/Documentation/devicetree/bindings/spi/mediatek,spi-mt65xx.yaml b/Documentation/devicetree/bindings/spi/mediatek,spi-mt65xx.yaml
> --- a/Documentation/devicetree/bindings/spi/mediatek,spi-mt65xx.yaml
> +++ b/Documentation/devicetree/bindings/spi/mediatek,spi-mt65xx.yaml
> @@ -39,6 +39,10 @@ properties:
> - mediatek,mt7988-spi-single
> - mediatek,mt8188-spi-ipm
> - const: mediatek,spi-ipm
> + - items:
> + - enum:
> + - mediatek,mtxxxx-spi
[Severity: Medium]
Is "mediatek,mtxxxx-spi" meant to be replaced with a concrete SoC name?
Device tree bindings must document the actual hardware SoC variants. In
properties.compatible, this placeholder will cause actual device tree files
using the real SoC compatible string alongside the "mediatek,spi-ipm-v59"
fallback to fail dtbs_check validation, while incorrectly passing the
meaningless "mtxxxx" placeholder.
> + - const: mediatek,spi-ipm-v59
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260924031211.2199921-1-Tim.Kuo@mediatek.com?part=1
next prev parent reply other threads:[~2026-09-24 3:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 3:12 [PATCH 1/2] dt-bindings: spi: mediatek: add mediatek,spi-ipm-v59 compatible Tim Kuo
2026-09-24 3:12 ` [PATCH 2/2] spi: mt65xx: support wider tick delay field on IPM v59 Tim Kuo
2026-09-24 3:19 ` sashiko-bot
2026-09-24 3:19 ` sashiko-bot [this message]
2026-09-24 12:17 ` [PATCH 1/2] dt-bindings: spi: mediatek: add mediatek,spi-ipm-v59 compatible Mark Brown
2026-09-24 17:28 ` Conor Dooley
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=20260924031928.DEEFC1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Tim.Kuo@mediatek.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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