[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6ebf4056-c6e0-495b-9e67-ca8d9dc8eae3@kernel.org>
Date: Thu, 4 Dec 2025 14:11:44 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Paul Sajna <sajattack@...tmarketos.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, David Heidelberg <david@...t.cz>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, phone-devel@...r.kernel.org,
~postmarketos/upstreaming@...ts.sr.ht, Amir Dahan <system64fumo@...a.io>,
Christopher Brown <crispybrown@...il.com>,
Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Subject: Re: [PATCH v5 01/12] arm64: dts: qcom: sdm845-lg-common: Sort nodes
and properties
On 03/12/2025 10:40, Paul Sajna wrote:
> Improve adherance to style guidelines below:
> https://docs.kernel.org/devicetree/bindings/dts-coding-style.html
>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
> Signed-off-by: Paul Sajna <sajattack@...tmarketos.org>
> ---
> arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi | 144 ++++++++++++++-----------
> 1 file changed, 82 insertions(+), 62 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi b/arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi
> index 0ee2f4b99fbd..b8ab64a8de1c 100644
> --- a/arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi
> @@ -38,11 +38,6 @@ reserved-memory {
> #size-cells = <2>;
> ranges;
>
> - qseecom_mem: memory@...00000 {
> - reg = <0 0xb2000000 0 0x1800000>;
> - no-map;
> - };
> -
> gpu_mem: memory@...15000 {
> reg = <0 0x8c415000 0 0x2000>;
> no-map;
> @@ -99,7 +94,12 @@ memory@...00000 {
> no-map;
> };
>
> - rmtfs_mem: rmtfs-region@...00000 {
Why?
> + qseecom_mem: memory@...00000 {
> + reg = <0 0xb2000000 0 0x1800000>;
> + no-map;
> + };
> +
> + rmtfs_mem: memory@...01000 {
No, you are doing much more then sorting. You are changing names to
incorrect ones and maybe (tricky to say) change also unit address to
buggy one.
@Konrad,
Why are we started resorting the addresses BEFORE we came up with proper
linter? Why the rule suddenly changed?
Best regards,
Krzysztof
Powered by blists - more mailing lists