public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Beleswar Padhi <b-padhi@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
	<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Cc: <afd@ti.com>, <u-kumar1@ti.com>, <hnagalla@ti.com>, <jm@ti.com>,
	<b-padhi@ti.com>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/2] TI: K3: Switch MCU R5F cluster into Split mode
Date: Thu, 22 May 2025 13:04:24 +0530	[thread overview]
Message-ID: <20250522073426.329344-1-b-padhi@ti.com> (raw)

Several TI K3 SoCs like J7200, J721E, J721S2, J784S4 and J742S2 have a
R5F cluster in the MCU domain which is configured for LockStep mode at
the moment. Switch this R5F cluster to Split mode by default in all
corresponding board level DTs to maximize the number of R5F cores.

Corresponding support to shutdown MCU R5F core 1 on SoC power on have
been posted in U-Boot:
https://lore.kernel.org/all/20250522071828.285462-1-b-padhi@ti.com/

While at it, correct the firmware-name property for MCU R5F cores of
J742S2 SoC in [PATCH 1/2].

Testing Done:
1. Tested that each patch does not generate any new warnings/errors.
2. Build test on all existing TI K3 platforms.
3. Tested U-Boot and Linux load of MCU R5F core in split mode on all
applicable boards (AM68-SK, AM69-SK, J7200-EVM, J721E-EVM, J721S2-EVM,
J784S4-evm, J742S2-EVM)

Test logs:
https://gist.github.com/3V3RYONE/ee8e3cb9aa5f4c5c00b059b9c14bfa98

Thanks,
Beleswar

Beleswar Padhi (2):
  arm64: dts: ti: k3-j742s2-mcu-wakeup: Override firmware-name for MCU
    R5F cores
  arm64: dts: ti: k3: Switch MCU R5F cluster to Split-mode

 arch/arm64/boot/dts/ti/k3-am68-sk-som.dtsi      |  4 ++++
 arch/arm64/boot/dts/ti/k3-am69-sk.dts           |  4 ++++
 arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi     |  4 ++++
 arch/arm64/boot/dts/ti/k3-j721e-sk.dts          |  4 ++++
 arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi     |  4 ++++
 arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi    |  4 ++++
 .../arm64/boot/dts/ti/k3-j742s2-mcu-wakeup.dtsi | 17 +++++++++++++++++
 arch/arm64/boot/dts/ti/k3-j742s2.dtsi           |  1 +
 .../dts/ti/k3-j784s4-j742s2-evm-common.dtsi     |  4 ++++
 9 files changed, 46 insertions(+)
 create mode 100644 arch/arm64/boot/dts/ti/k3-j742s2-mcu-wakeup.dtsi

-- 
2.34.1


             reply	other threads:[~2025-05-22  7:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-22  7:34 Beleswar Padhi [this message]
2025-05-22  7:34 ` [PATCH 1/2] arm64: dts: ti: k3-j742s2-mcu-wakeup: Override firmware-name for MCU R5F cores Beleswar Padhi
2025-05-22  7:34 ` [PATCH 2/2] arm64: dts: ti: k3: Switch MCU R5F cluster to Split-mode Beleswar Padhi
2025-05-22 15:53 ` [PATCH 0/2] TI: K3: Switch MCU R5F cluster into Split mode Nishanth Menon
2025-05-23  8:57   ` Beleswar Prasad Padhi
2025-05-23 11:48     ` Nishanth Menon
2025-05-23 13:16       ` Andrew Davis
2025-05-27 18:14         ` Kumar, Udit
2025-05-27  6:09       ` Beleswar Prasad Padhi

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=20250522073426.329344-1-b-padhi@ti.com \
    --to=b-padhi@ti.com \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hnagalla@ti.com \
    --cc=jm@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=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