From: Nishanth Menon <nm@ti.com>
To: Manorit Chawdhry <m-chawdhry@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>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 0/9] Introduce J742S2 SoC and EVM
Date: Wed, 7 Aug 2024 08:25:05 -0500 [thread overview]
Message-ID: <20240807132505.4aqvgsdck7pzk6kv@impale> (raw)
In-Reply-To: <20240731-b4-upstream-j742s2-v3-0-da7fe3aa9e90@ti.com>
On 22:40-20240731, Manorit Chawdhry wrote:
> The series adds support for J742S2 family of SoCs. Also adds J742S2 EVM
> Support and re-uses most of the stuff from the superset device J784s4.
>
> It initially cleans up the J784s4 SoC files so that they can be
> re-usable for j742s2 by introducing -common files. Next it cleans up the
> EVM files for j784s4 in a similar way and then goes about adding the
> support for j742s2.
>
> Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
> ---
> Changes in v3:
> * Nishanth
> - Update copyright string
> - Add TRM link in SoC file.
> - Refactor to split out common soc support between j742s2 and j784s4
>
> - Add DTC_FLAGS as well for j742s2
> - Link to v2: https://lore.kernel.org/r/20240730-b4-upstream-j742s2-v2-0-6aedf892156c@ti.com
>
> ---
> Manorit Chawdhry (9):
> arm64: dts: ti: Move j784s4-{} include files to j784s4-j742s2-{}-common.dtsi
> arm64: dts: ti: Move k3-j784s4.dtsi to k3-j784s4-j742s2-common.dtsi
> arm64: dts: ti: Split k3-j784s4-j742s2-common.dtsi
> arm64: dts: ti: Split k3-j784s4-j742s2-main-common.dtsi
The above 4 patches can be merged into a single patch under SoC
refactoring.
> arm64: dts: ti: Move k3-j784s4-evm.dts to k3-j784s4-j742s2-evm-common.dtsi
> arm64: dts: ti: Split k3-j784s4-j742s2-evm-common.dtsi
The above two patches can be squashed to be a single patch for evm
refactoring.
> dt-bindings: arm: ti: Add bindings for J742S2 SoCs and Boards
> arm64: dts: ti: Introduce J742S2 SoC family
> arm64: dts: ti: Add support for J742S2 EVM board
Also it is not clear how cpsw/serdes and pcie changes are handled
here.
>
> Documentation/devicetree/bindings/arm/ti/k3.yaml | 6 +
> arch/arm64/boot/dts/ti/Makefile | 4 +
> arch/arm64/boot/dts/ti/k3-j742s2-evm.dts | 26 +
> arch/arm64/boot/dts/ti/k3-j742s2-main.dtsi | 45 +
> arch/arm64/boot/dts/ti/k3-j742s2.dtsi | 98 +
> arch/arm64/boot/dts/ti/k3-j784s4-evm.dts | 1422 +---------
> .../arm64/boot/dts/ti/k3-j784s4-j742s2-common.dtsi | 150 ++
> .../boot/dts/ti/k3-j784s4-j742s2-evm-common.dtsi | 1436 ++++++++++
> .../boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi | 2772 ++++++++++++++++++++
> ...tsi => k3-j784s4-j742s2-mcu-wakeup-common.dtsi} | 2 +-
> ...l.dtsi => k3-j784s4-j742s2-thermal-common.dtsi} | 0
> arch/arm64/boot/dts/ti/k3-j784s4-main.dtsi | 2764 -------------------
> arch/arm64/boot/dts/ti/k3-j784s4.dtsi | 135 +-
> 13 files changed, 4540 insertions(+), 4320 deletions(-)
> ---
> base-commit: cd19ac2f903276b820f5d0d89de0c896c27036ed
> change-id: 20240620-b4-upstream-j742s2-7ba652091550
>
> Best regards,
> --
> Manorit Chawdhry <m-chawdhry@ti.com>
>
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
prev parent reply other threads:[~2024-08-07 13:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 17:10 [PATCH v3 0/9] Introduce J742S2 SoC and EVM Manorit Chawdhry
2024-07-31 17:10 ` [PATCH v3 1/9] arm64: dts: ti: Move j784s4-{} include files to j784s4-j742s2-{}-common.dtsi Manorit Chawdhry
2024-07-31 17:10 ` [PATCH v3 2/9] arm64: dts: ti: Move k3-j784s4.dtsi to k3-j784s4-j742s2-common.dtsi Manorit Chawdhry
2024-07-31 17:10 ` [PATCH v3 3/9] arm64: dts: ti: Split k3-j784s4-j742s2-common.dtsi Manorit Chawdhry
2024-07-31 17:10 ` [PATCH v3 4/9] arm64: dts: ti: Split k3-j784s4-j742s2-main-common.dtsi Manorit Chawdhry
2024-08-07 13:09 ` Nishanth Menon
2024-08-07 13:20 ` Nishanth Menon
2024-08-08 4:52 ` Manorit Chawdhry
2024-08-08 5:28 ` Siddharth Vadapalli
2024-08-08 10:54 ` Nishanth Menon
2024-08-08 4:56 ` Manorit Chawdhry
2024-08-08 10:48 ` Nishanth Menon
2024-07-31 17:10 ` [PATCH v3 5/9] arm64: dts: ti: Move k3-j784s4-evm.dts to k3-j784s4-j742s2-evm-common.dtsi Manorit Chawdhry
2024-07-31 17:10 ` [PATCH v3 6/9] arm64: dts: ti: Split k3-j784s4-j742s2-evm-common.dtsi Manorit Chawdhry
2024-08-07 13:06 ` Nishanth Menon
2024-07-31 17:10 ` [PATCH v3 7/9] dt-bindings: arm: ti: Add bindings for J742S2 SoCs and Boards Manorit Chawdhry
2024-07-31 17:10 ` [PATCH v3 8/9] arm64: dts: ti: Introduce J742S2 SoC family Manorit Chawdhry
2024-07-31 17:10 ` [PATCH v3 9/9] arm64: dts: ti: Add support for J742S2 EVM board Manorit Chawdhry
2024-08-07 9:41 ` Beleswar Prasad Padhi
2024-08-07 11:51 ` Nishanth Menon
2024-08-07 12:06 ` Nishanth Menon
2024-08-07 13:25 ` Nishanth Menon [this message]
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=20240807132505.4aqvgsdck7pzk6kv@impale \
--to=nm@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=krzysztof.kozlowski@linaro.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