public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Andrew Davis <afd@ti.com>
To: Manorit Chawdhry <m-chawdhry@ti.com>, Nishanth Menon <nm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Udit Kumar <u-kumar1@ti.com>,
	Neha Malcom Francis <n-francis@ti.com>,
	Aniket Limaye <a-limaye@ti.com>
Subject: Re: [PATCH v2 2/3] arm64: dts: ti: Introduce J742S2 SoC family
Date: Wed, 31 Jul 2024 09:37:23 -0500	[thread overview]
Message-ID: <087ee9e2-50ec-4791-a534-b3ebbf594fe6@ti.com> (raw)
In-Reply-To: <20240731135714.p53lki7mihzxcyk2@uda0497581>

On 7/31/24 8:57 AM, Manorit Chawdhry wrote:
> Hi Nishanth,
> 
> On 06:06-20240731, Nishanth Menon wrote:
>> On 09:49-20240731, Manorit Chawdhry wrote:
>>>>> + */
>>>>> +
>>>>> +#include "k3-j784s4.dtsi"
>>>>> +
>>>>> +/ {
>>>>> +	model = "Texas Instruments K3 J742S2 SoC";
>>>>> +	compatible = "ti,j742s2";
>>>>> +
>>>>> +	cpus {
>>>>> +		cpu-map {
>>>>> +			/delete-node/ cluster1;
>>>>> +		};
>>>>> +	};
>>>>> +
>>>>> +	/delete-node/ cpu4;
>>>>> +	/delete-node/ cpu5;
>>>>> +	/delete-node/ cpu6;
>>>>> +	/delete-node/ cpu7;
>>>>
>>>> I suggest refactoring by renaming the dtsi files as common and split out
>>>> j784s4 similar to j722s/am62p rather than using /delete-node/
>>>>
>>>
>>> I don't mind the suggestion Nishanth if there is a reason behind it.
>>> Could you tell why we should not be using /delete-node/?
>>>
>>
>> Maintenance, readability and sustenance are the reasons. This is a
>> optimized die. It will end up having it's own changes in property
>> and integration details. While reuse is necessary, modifying the
>> properties with overrides and /delete-nodes/ creates maintenance
>> challenges down the road. We already went down this road with am62p
>> reuse with j722s, and eventually determined split and reuse is the
>> best option. See [1] for additional guidance.
>>
>>
>> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/dts-coding-style.rst#n189
> 
> Thank you for giving some reasoning, would do the needful!
> 

This refactor will require some interesting naming for the
common SoC files. Based on your name for the EVM, I'm guessing
you will go with

k3-j784s4-common.dtsi

included from the real k3-j784s4.dtsi and the new k3-j742s2.dtsi?

Too bad the Jacinto SoC names don't use a hierarchical naming. :(

J7<family><part><spin><etc>..

Andrew

> Regards,
> Manorit
> 
>>
>> -- 
>> Regards,
>> Nishanth Menon
>> Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
> 


  reply	other threads:[~2024-07-31 14:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30  7:13 [PATCH v2 0/3] Introduce J742S2 SoC and EVM Manorit Chawdhry
2024-07-30  7:13 ` [PATCH v2 1/3] dt-bindings: arm: ti: Add bindings for J742S2 SoCs and Boards Manorit Chawdhry
2024-07-30  7:40   ` Krzysztof Kozlowski
2024-07-30  7:13 ` [PATCH v2 2/3] arm64: dts: ti: Introduce J742S2 SoC family Manorit Chawdhry
2024-07-30 12:33   ` Nishanth Menon
2024-07-31  4:19     ` Manorit Chawdhry
2024-07-31 11:06       ` Nishanth Menon
2024-07-31 13:57         ` Manorit Chawdhry
2024-07-31 14:37           ` Andrew Davis [this message]
2024-07-31 14:58             ` Manorit Chawdhry
2024-07-31 15:03               ` Andrew Davis
2024-07-31 15:18                 ` Manorit Chawdhry
2024-07-31 15:34                   ` Nishanth Menon
2024-07-30  7:13 ` [PATCH v2 3/3] arm64: dts: ti: Add support for J742S2 EVM board Manorit Chawdhry
2024-07-31 14:46   ` Andrew Davis
2024-07-31 15:23     ` Manorit Chawdhry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=087ee9e2-50ec-4791-a534-b3ebbf594fe6@ti.com \
    --to=afd@ti.com \
    --cc=a-limaye@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-chawdhry@ti.com \
    --cc=n-francis@ti.com \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox