linux-kernel - Re: [PATCH 5/5] arm64: dts: ti: k3-am62a: use a specific MCU controller compatible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d922f7b7-0e9f-4485-b746-0cf968dca570@kernel.org>
Date: Mon, 20 May 2024 14:40:36 +0300
From: Roger Quadros <rogerq@...nel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>,
 Kishon Vijay Abraham I <kishon@...nel.org>, Nishanth Menon <nm@...com>,
 Vignesh Raghavendra <vigneshr@...com>, Tero Kristo <kristo@...nel.org>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 5/5] arm64: dts: ti: k3-am62a: use a specific MCU
 controller compatible



On 18/05/2024 23:07, Krzysztof Kozlowski wrote:
> SoCs (and associated MCUs) should use dedicated compatibles for their
> nodes, not re-use one coming from an another SoC.  Using an incorrect
> compatible does not allow to properly match/validate children of the
> MCU device and causes dtbs_check warnings:
> 
>   k3-am62a7-sk.dtb: syscon@...00000: 'syscon@...8', 'syscon@...8' do not match any of the regexes:
>     '^chipid@[0-9a-f]+$', '^clock-controller@[0-9a-f]+$', '^mux-controller@[0-9a-f]+$', 'phy@[0-9a-f]+$', 'pinctrl-[0-9]+'
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>

Reviewed-by: Roger Quadros <rogerq@...nel.org>

-- 
cheers,
-roger