mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Apurva Nandan <a-nandan@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] arm64: dts: ti: k3-j72xx-main: Switch MAIN R5F clusters to Split-mode
Date: Wed, 29 Mar 2023 12:07:26 +0530	[thread overview]
Message-ID: <20230329063728.14126-1-a-nandan@ti.com> (raw)

J721E and J7200 SoCs have two R5F clusters in the MAIN domain, and both
of these are configured for LockStep mode at the moment. Switch both of
these R5F clusters to Split mode by default to maximize the number of
R5F cores. The MCU R5F cluster continues to be in the preferred LockStep
mode.

Note that this configuration is the default for remoteproc mode (kernel
driver boots the R5F processors). These will be overridden for early-
booted remoteprocs through the corresponding IPC-only support in the K3
R5F remoteproc driver.

Suman Anna (2):
  arm64: dts: ti: k3-j721e-main: Switch MAIN R5F clusters to Split-mode
  arm64: dts: ti: k3-j7200-main: Switch MAIN R5F cluster to Split-mode

 arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 2 +-
 arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-03-29  6:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-29  6:37 Apurva Nandan [this message]
2023-03-29  6:37 ` [PATCH 1/2] arm64: dts: ti: k3-j721e-main: " Apurva Nandan
2023-03-29 12:48   ` Nishanth Menon
2023-03-29  6:37 ` [PATCH 2/2] arm64: dts: ti: k3-j7200-main: Switch MAIN R5F cluster " Apurva Nandan
2023-03-29 12:49   ` Nishanth Menon

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=20230329063728.14126-1-a-nandan@ti.com \
    --to=a-nandan@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --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

all inboxes | Powered by JetHome®