Re: [PATCH v2 1/3] arm64: dts: ti: k3-am62: use ti,am62-m_can compatible for m_can devices

[sashiko-bot@kernel.org]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch introduces a new device tree compatible string 'ti,am62-m_can' without updating the corresponding device tree binding schema, which will cause dtbs_check validation failures.
--

commit aab89344d119641f5683480ba4bd99f51381ae13
Author: Kendall Willis <k-willis@ti.com>

arm64: dts: ti: k3-am62: use ti,am62-m_can compatible for m_can devices

This commit prepends the "ti,am62-m_can" compatible string to the m_can
devices in the k3-am62-mcu device tree. This change reflects the out-of-band
wakeup functionality available for these devices during deeper low power
states.

> diff --git a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
> --- a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
> @@ -152,7 +152,7 @@ mcu_rti0: watchdog@4880000 {
>  	};
>  
>  	mcu_mcan0: can@4e08000 {
> -		compatible = "bosch,m_can";
> +		compatible = "ti,am62-m_can", "bosch,m_can";

[Severity: Low]
Will adding "ti,am62-m_can" here trigger a dtbs_check validation failure?

The existing schema for the Bosch M_CAN controller in
Documentation/devicetree/bindings/net/can/bosch,m_can.yaml expects the
compatible property to strictly be bosch,m_can. 

Changing it to an array without updating the YAML schema will likely cause
DT validation tools to fail during the build process.

Should the binding schema be updated alongside this change?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260902-smth-v2-0-b3678ca44c7b@ti.com?part=1