From: Brandon Brnich <b-brnich@ti.com>
To: <nm@ti.com>, <vigneshr@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>
Cc: <afd@ti.com>, <b-brnich@ti.com>
Subject: [PATCH v3 2/4] arm64: dts: ti: k3-j721s2-main: Assign SRAM to VPU node
Date: Mon, 21 Sep 2026 13:48:48 -0500 [thread overview]
Message-ID: <20260921184850.3810018-3-b-brnich@ti.com> (raw)
In-Reply-To: <20260921184850.3810018-1-b-brnich@ti.com>
The Wave5 VPU supports connecting to on-chip SRAM through its secondary
AXI interface. This allows temporal buffers to be stored on a per-stream
basis, reducing DDR memory traffic.
Signed-off-by: Brandon Brnich <b-brnich@ti.com>
Reviewed-by: Andrew Davis <afd@ti.com>
---
arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi
index 1fd173a68c0b2..233aedcbf2ec3 100644
--- a/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi
@@ -716,6 +716,7 @@ vpu: video-codec@4210000 {
interrupts = <GIC_SPI 182 IRQ_TYPE_LEVEL_HIGH>;
clocks = <&k3_clks 179 2>;
power-domains = <&k3_pds 179 TI_SCI_PD_EXCLUSIVE>;
+ sram = <&main_navss_sram>;
};
main_sdhci0: mmc@4f80000 {
--
2.43.0
next prev parent reply other threads:[~2026-09-21 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 18:48 [PATCH v3 0/4] Add SRAM Nodes for VPU Brandon Brnich
2026-09-21 18:48 ` [PATCH v3 1/4] arm64: dts: ti: k3-j721s2-main: Add mmio-sram node to main_navss Brandon Brnich
2026-09-21 18:48 ` Brandon Brnich [this message]
2026-09-21 18:48 ` [PATCH v3 3/4] arm64: dts: ti: k3-am62a-main: Assign SRAM to VPU node Brandon Brnich
2026-09-21 18:48 ` [PATCH v3 4/4] arm64: dts: ti: k3-am62p-j722s-common-main: " Brandon Brnich
2026-09-28 17:19 ` [PATCH v3 0/4] Add SRAM Nodes for VPU 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=20260921184850.3810018-3-b-brnich@ti.com \
--to=b-brnich@ti.com \
--cc=afd@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