[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240731153458.7o3i2xcjvn22igxa@squatted>
Date: Wed, 31 Jul 2024 10:34:58 -0500
From: Nishanth Menon <nm@...com>
To: Manorit Chawdhry <m-chawdhry@...com>
CC: Andrew Davis <afd@...com>, Vignesh Raghavendra <vigneshr@...com>,
Tero
Kristo <kristo@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof
Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
<linux-arm-kernel@...ts.infradead.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Udit Kumar <u-kumar1@...com>,
Neha Malcom
Francis <n-francis@...com>,
Aniket Limaye <a-limaye@...com>
Subject: Re: [PATCH v2 2/3] arm64: dts: ti: Introduce J742S2 SoC family
On 20:48-20240731, Manorit Chawdhry wrote:
[...]
> Yeah, was gonna go with that file only right now, but now would I have
>
> - k3-j784s4-mcu-wakeup-common.dtsi ( this is not required at this stage,
> but ig for consistency better to now itself )
> - k3-j784s4-main-common.dtsi ( all dsps excluding c7x_3 )
> - k3-j784s4-thermal-common.dtsi ( not required again but consistency )
> - k3-j784s4-common.dtsi ( all this won't have the cpu but will have all
> other ranges including for the last dsp and all )
We already use k3-am62p-j722s-common-main.dtsi so that people don't
ask what is this common to and track down via grep who is including
what. I'd rather us follow that convention for now that debate is done
with and integrated in master. I don't see a strong reason yet to change
the same. Again, everyone will have an subjective opinion, I prefer to
follow existing convention that is established on topics that are
cosmetic.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists