From: Nishanth Menon <nm@ti.com>
To: Paresh Bhagat <p-bhagat@ti.com>
Cc: <vigneshr@ti.com>, <praneeth@ti.com>, <kristo@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<khasim@ti.com>, <v-singh1@ti.com>, <afd@ti.com>
Subject: Re: [PATCH v2 1/3] dt-bindings: arm: ti: Add bindings for AM62D2 SoC
Date: Mon, 5 May 2025 08:03:03 -0500 [thread overview]
Message-ID: <20250505130303.x56xnmww5mzohahn@reentry> (raw)
In-Reply-To: <e7ddd359-bf19-4f6a-af32-43bcb5504ab1@ti.com>
On 15:01-20250505, Paresh Bhagat wrote:
> On 02/05/25 21:35, Nishanth Menon wrote:
[...]
> > Looking at the board patch in the series, this is am62p5 ? what is the
> > difference? If there is a difference, why is there no dtsi
> > file for am62d?
> AM62d2 SoC is similar to AM62a7 in terms of CPU cores, cache hierarchy and
Looking at the block diagram side to side, I am unable to see any
difference - it looks like "similar" is "same" ?
> other peripherals. https://lore.kernel.org/linux-arm-kernel/20220901141328.899100-5-vigneshr@ti.com/
> Thus same dtsi file is being reused here.
So, if there is no difference at all, why this series? Commit message
does need to specify why exactly what is different and why we are
re-using. If there is no difference what so ever, then we follow what we
have done in K3 architecture so far, which is just to introduce a board
file (assuming there is difference there Vs what is supported already).
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2025-05-05 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 15:39 [PATCH v2 0/3] Add support for AM62D2 SoC and EVM Paresh Bhagat
2025-05-02 15:39 ` [PATCH v2 1/3] dt-bindings: arm: ti: Add bindings for AM62D2 SoC Paresh Bhagat
2025-05-02 16:05 ` Nishanth Menon
2025-05-05 9:31 ` Paresh Bhagat
2025-05-05 13:03 ` Nishanth Menon [this message]
2025-05-02 15:39 ` [PATCH v2 2/3] arm64: dts: ti: Add pinctrl entries for AM62D2 family of SoCs Paresh Bhagat
2025-05-02 16:55 ` Andrew Davis
2025-05-02 15:39 ` [PATCH v2 3/3] arm64: dts: ti: Add support for AM62D2-EVM Paresh Bhagat
2025-05-02 20:07 ` Bryan Brattlof
2025-05-05 9:13 ` Paresh Bhagat
2025-05-05 12:12 ` Bryan Brattlof
2025-05-03 5:54 ` kernel test robot
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=20250505130303.x56xnmww5mzohahn@reentry \
--to=nm@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=khasim@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p-bhagat@ti.com \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=v-singh1@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