Re: [PATCH 3/7] arm/arm64: dts: mediatek: drop mt6589 fallback from watchdog

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Critical] Removing the fallback compatible string 'mediatek,mt6589-wdt' from device trees breaks forward compatibility (ABI breakage) with older kernels.

Device trees are treated as a stable ABI in Linux, meaning a newly compiled Device Tree Blob (DTB) must be able to boot successfully on older kernels. Older LTS/stable kernels rely entirely on the generic 'mediatek,mt6589-wdt' fallback string to probe the watchdog driver for these Mediatek SoCs (e.g., mt2701, mt6572, mt8173), because older driver versions do not include the SoC-specific strings in their `of_match_table`.

By removing the fallback string from the `.dtsi` files, a new DTB will fail to bind the watchdog driver on any older kernel. Because this watchdog driver also registers the system's reset controller (`toprgu_register_reset_controller()`), its failure to probe will cascade, breaking other devices that depend on those resets.

Although the previous patch in this series added the specific compatibles to the new kernel's driver, standard Device Tree practice dictates that valid fallback strings must not be removed once they have been established, precisely to preserve compatibility with older kernels.
--

--- Patch [3]: [PATCH 3/7] arm/arm64: dts: mediatek: drop mt6589 fallback from watchdog ---
commit 32f0d12ddf1053eabd5133b535f4e55a874b71e9
Author: Akari Tsuyukusa <akkun11.open@gmail.com>

arm/arm64: dts: mediatek: drop mt6589 fallback from watchdog

This commit removes the "mediatek,mt6589-wdt" fallback string from several
Mediatek device trees, leaving only the SoC-specific compatibles.

> diff --git a/arch/arm/boot/dts/mediatek/mt2701.dtsi b/arch/arm/boot/dts/mediatek/mt2701.dtsi
> index 128b87229f3d5..f23a6d860a53b 100644
> --- a/arch/arm/boot/dts/mediatek/mt2701.dtsi
> +++ b/arch/arm/boot/dts/mediatek/mt2701.dtsi
> @@ -160,8 +160,7 @@ scpsys: power-controller@10006000 {
>  	};
>  
>  	watchdog: watchdog@10007000 {
> -		compatible = "mediatek,mt2701-wdt",
> -			     "mediatek,mt6589-wdt";
> +		compatible = "mediatek,mt2701-wdt";

[Severity: Critical]
Does removing the fallback string break ABI forward compatibility with older
kernels?

Device trees are typically treated as a stable ABI, meaning a newly compiled
DTB needs to boot successfully on older kernels. Older LTS or stable kernels
might rely entirely on the generic "mediatek,mt6589-wdt" fallback string to
probe the watchdog driver for these Mediatek SoCs, because older driver
versions do not include the SoC-specific strings in their of_match_table.

By removing the fallback string here and in the other included dtsi files,
will a new DTB fail to bind the watchdog driver on an older kernel? Because
this watchdog driver also registers the system's reset controller, this
failure could cascade and break other devices that depend on those resets.

>  		reg = <0 0x10007000 0 0x100>;
>  	};
>  

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260716161923.266315-1-akkun11.open@gmail.com?part=3