[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4cdada61-3861-49e9-b8a4-bd08f8435da8@linaro.org>
Date: Wed, 19 Jun 2024 07:54:15 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Jan Kiszka <jan.kiszka@...mens.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Kishon Vijay Abraham I <kishon@...nel.org>,
Roger Quadros <rogerq@...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, "Andrew F. Davis" <afd@...com>
Subject: Re: [PATCH 0/5] ti: fix dtbs_check for some syscon bindings and DTS
node
On 19/06/2024 06:58, Jan Kiszka wrote:
> On 18.05.24 22:07, Krzysztof Kozlowski wrote:
>> Hi,
>>
>> I am in the process of fixing syscon/simple-mfd bindings (to be posted
>> separately) and found set of issues in TI looking independent of my
>> series. Please apply via TI SoC.
>>
>> Best regards,
>> Krzysztof
>>
>> ---
>> Krzysztof Kozlowski (5):
>> dt-bindings: soc: ti: am62-system-controller: add AM62 syscon
>> dt-bindings: soc: ti: am645-system-controller: add AM654 syscon
>> arm64: dts: ti: k3-am62: add dedicated wakeup controller compatible
>> arm64: dts: ti: k3-am65-mcu: add dedicated wakeup controller compatible
>> arm64: dts: ti: k3-am62a: use a specific MCU controller compatible
>>
>> .../bindings/soc/ti/ti,am62-system-controller.yaml | 77 ++++++++++++++++++++++
>> .../soc/ti/ti,am654-system-controller.yaml | 60 +++++++++++++++++
>> arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 2 +-
>> arch/arm64/boot/dts/ti/k3-am62a-wakeup.dtsi | 2 +-
>> arch/arm64/boot/dts/ti/k3-am65-mcu.dtsi | 2 +-
>> 5 files changed, 140 insertions(+), 3 deletions(-)
>> ---
>> base-commit: e032bb82c315d2317a80506195d16ce4308d8cf7
>> change-id: 20240518-dt-bindings-ti-soc-mfd-ac211578d7a5
>>
>> Best regards,
>
> Good to see progress here! Helps us finding our own issues while adding
> things to the affected targets.
>
> But you didn't address this ones yet:
>
> .../arch/arm64/boot/dts/ti/k3-am654-base-board.dtb: scm-conf@...000: compatible: ['syscon', 'simple-mfd'] is too short
> from schema $id: http://devicetree.org/schemas/mfd/syscon.yaml#
> (plus our IOT2050 boards, all via k3-am65-main.dtsi)
>
> And a number of other boards seem to lack adoption of the new wakeup
> controller binding if I get this correctly:
>
> .../arch/arm64/boot/dts/ti/k3-j7200-common-proc-board.dtb: syscon@...00000: compatible: ['syscon', 'simple-mfd'] is too short
> from schema $id: http://devicetree.org/schemas/mfd/syscon.yaml#
> .../arch/arm64/boot/dts/ti/k3-j721e-beagleboneai64.dtb: syscon@...00000: compatible: ['syscon', 'simple-mfd'] is too short
> from schema $id: http://devicetree.org/schemas/mfd/syscon.yaml#
> DTC_CHK arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dtb
> .../arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dtb: syscon@...00000: compatible: ['syscon', 'simple-mfd'] is too short
> from schema $id: http://devicetree.org/schemas/mfd/syscon.yaml#
> .../arch/arm64/boot/dts/ti/k3-j721e-sk.dtb: syscon@...00000: compatible: ['syscon', 'simple-mfd'] is too short
> from schema $id: http://devicetree.org/schemas/mfd/syscon.yaml#
> DTC_CHK arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dtb
> .../arch/arm64/boot/dts/ti/k3-am68-sk-base-board.dtb: syscon@...00000: compatible: ['syscon', 'simple-mfd'] is too short
> from schema $id: http://devicetree.org/schemas/mfd/syscon.yaml#
> DTC_CHK arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dtb
> .../arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dtb: syscon@...00000: compatible: ['syscon', 'simple-mfd'] is too short
> from schema $id: http://devicetree.org/schemas/mfd/syscon.yaml#
>
> Forgotten?
There are just too many warnings to be fixed.
Best regards,
Krzysztof
Powered by blists - more mailing lists