From: sashiko-bot@kernel.org
To: "Andrew Gaylard" <ag@ffroot.co.za>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/6] arm: dts: sunplus: add PWM, watchdog and MMC nodes to SP7021 DTSI
Date: Mon, 21 Sep 2026 18:34:55 +0000 [thread overview]
Message-ID: <20260921183456.247A81F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260921182620.17597-4-ag@ffroot.co.za>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt: board-specific MMC properties hardcoded in SoC-level .dtsi
--
commit 17776a65b44f3bc151f243f012bdb8edd8912aba
Author: Andrew Gaylard <ag@ffroot.co.za>
arm: dts: sunplus: add PWM, watchdog and MMC nodes to SP7021 DTSI
This commit adds device nodes for the PWM controller, Watchdog controller,
and eMMC controller to the SP7021 generic SoC device tree include file.
It also adds a label to the gpio-leds node to allow overrides by board files.
> diff --git a/arch/arm/boot/dts/sunplus/sunplus-sp7021.dtsi b/arch/arm/boot/dts/sunplus/sunplus-sp7021.dtsi
> index ae9bbe0320b8d..17185238e7ba7 100644
> --- a/arch/arm/boot/dts/sunplus/sunplus-sp7021.dtsi
> +++ b/arch/arm/boot/dts/sunplus/sunplus-sp7021.dtsi
[ ... ]
> + mmc0: mmc@3b00 {
> + compatible = "sunplus,sp7021-mmc";
> + reg = <0x3b00 0x180>;
> + interrupts = <20 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&clkc CLK_CARD_CTL0>;
> + resets = <&rstc RST_CARD_CTL0>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&emmc_pins>;
> + bus-width = <8>;
> + max-frequency = <52000000>;
> + non-removable;
> + disable-wp;
> + cap-mmc-highspeed;
> + mmc-ddr-3_3v;
> + no-sdio;
> + no-sd;
[Severity: Low]
Are these board-specific form-factor and electronic configurations appropriate
for the generic SoC-level dtsi file?
Hardcoding properties like non-removable, bus-width = <8>, no-sd, and no-sdio
in the generic SoC definition violates Device Tree design principles. If a
future board based on this SoC routes the mmc0 controller differently, such
as to a removable SD card slot, it will inherit these inappropriate properties.
Does this mean developers would have to use cumbersome /delete-property/
directives in their board dts files to undo the SoC-level configuration just
to make an SD card work?
> + status = "disabled";
> + };
> };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260921182620.17597-1-ag@ffroot.co.za?part=3
next prev parent reply other threads:[~2026-09-21 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 18:26 [PATCH v3 0/6] arm: sunplus: add Tibbo LTPP3G2 board support Andrew Gaylard
2026-09-21 18:26 ` [PATCH v3 1/6] dt-bindings: vendor-prefixes: Add Tibbo Andrew Gaylard
2026-09-21 18:26 ` [PATCH v3 2/6] dt-bindings: arm: sunplus: add Tibbo LTPP3G2 board compatible string Andrew Gaylard
2026-09-21 18:26 ` [PATCH v3 3/6] arm: dts: sunplus: add PWM, watchdog and MMC nodes to SP7021 DTSI Andrew Gaylard
2026-09-21 18:34 ` sashiko-bot [this message]
2026-09-21 18:26 ` [PATCH v3 4/6] arm: sunplus: enable SMP via PSCI on SP7021 Andrew Gaylard
2026-09-21 18:30 ` sashiko-bot
2026-09-21 18:26 ` [PATCH v3 5/6] arm: dts: sunplus: add Tibbo LTPP3G2 board Andrew Gaylard
2026-09-21 18:26 ` [PATCH v3 6/6] configs: sp7021: fix defaults and enable existing device drivers Andrew Gaylard
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=20260921183456.247A81F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=ag@ffroot.co.za \
--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