mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hari Nagalla <hnagalla@ti.com>
To: <nm@ti.com>, <vigneshr@ti.com>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>, <kristo@kernel.org>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	Hari Nagalla <hnagalla@ti.com>
Subject: [PATCH] arm64: dts: ti: k3-am62-main: Correct PRU core IRAM size
Date: Tue, 3 Mar 2026 20:30:12 -0600	[thread overview]
Message-ID: <20260304023012.20452-1-hnagalla@ti.com> (raw)

Each PRU core in the AM62x PRU subsystem has 16KB of program memory.
Correct the PRU device tree node reg property accordingly.

AM625 data sheet : https://www.ti.com/lit/ds/symlink/am625.pdf

Signed-off-by: Hari Nagalla <hnagalla@ti.com>
---
 arch/arm64/boot/dts/ti/k3-am62-main.dtsi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
index c5ee263d34a6..1bec89b1e378 100644
--- a/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-am62-main.dtsi
@@ -1213,7 +1213,7 @@ pruss_intc: interrupt-controller@20000 {
 
 		pru0: pru@34000 {
 			compatible = "ti,am625-pru";
-			reg = <0x34000 0x3000>,
+			reg = <0x34000 0x4000>,
 			      <0x22000 0x100>,
 			      <0x22400 0x100>;
 			reg-names = "iram", "control", "debug";
@@ -1225,7 +1225,7 @@ pru0: pru@34000 {
 
 		pru1: pru@38000 {
 			compatible = "ti,am625-pru";
-			reg = <0x38000 0x3000>,
+			reg = <0x38000 0x4000>,
 			      <0x24000 0x100>,
 			      <0x24400 0x100>;
 			reg-names = "iram", "control", "debug";
-- 
2.34.1


             reply	other threads:[~2026-03-04  2:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  2:30 Hari Nagalla [this message]
2026-03-09  4:26 ` Vignesh Raghavendra

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=20260304023012.20452-1-hnagalla@ti.com \
    --to=hnagalla@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=nm@ti.com \
    --cc=robh@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®