[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <29841f64-360b-1426-e1fd-dd4c64ee5455@linaro.org>
Date: Sun, 29 Jan 2023 11:42:12 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Kukjin Kim <kgene@...nel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: replicant@...osl.org, phone-devel@...r.kernel.org,
~postmarketos/upstreaming@...ts.sr.ht,
Martin Jücker <martin.juecker@...il.com>,
Henrik Grimler <henrik@...mler.se>,
Chanwoo Choi <cw00.choi@...sung.com>
Subject: Re: [PATCH 5/9] ARM: dts: exynos: move exynos-bus nodes out of soc in
Exynos4412
On 25/01/2023 10:45, Krzysztof Kozlowski wrote:
> The soc node is supposed to have only device nodes with MMIO addresses,
> as reported by dtc W=1:
>
> exynos4412.dtsi:407.20-413.5:
> Warning (simple_bus_reg): /soc/bus-acp: missing or empty reg/ranges property
>
> and dtbs_check:
>
> exynos4412-i9300.dtb: soc: bus-acp:
> {'compatible': ['samsung,exynos-bus'], 'clocks': [[7, 456]], 'clock-names': ['bus'], 'operating-points-v2': [[132]], 'status': ['okay'], 'devfreq': [[117]]} should not be valid under {'type': 'object'}
>
> Move the bus nodes and their OPP tables out of SoC to fix this.
> Re-order them alphabetically while moving and put some of the OPP tables
> in device nodes (if they are not shared).
>
Applied.
Best regards,
Krzysztof
Powered by blists - more mailing lists