public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Manorit Chawdhry <m-chawdhry@ti.com>
Cc: Andrew Davis <afd@ti.com>, 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 10:34:58 -0500	[thread overview]
Message-ID: <20240731153458.7o3i2xcjvn22igxa@squatted> (raw)
In-Reply-To: <20240731151820.tf6tzgj2wrc5vh5j@uda0497581>

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


  reply	other threads:[~2024-07-31 15:36 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
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 [this message]
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=20240731153458.7o3i2xcjvn22igxa@squatted \
    --to=nm@ti.com \
    --cc=a-limaye@ti.com \
    --cc=afd@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=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