From: Andrew Davis <afd@ti.com>
To: Brandon Brnich <b-brnich@ti.com>, <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>
Subject: Re: [PATCH v2 0/6] Add SRAM Nodes for VPU
Date: Tue, 11 Aug 2026 09:47:28 -0500 [thread overview]
Message-ID: <265d3c78-c7ae-4d0f-b6c0-5f9500121d86@ti.com> (raw)
In-Reply-To: <20260810205206.685971-1-b-brnich@ti.com>
On 8/10/26 3:52 PM, Brandon Brnich wrote:
> Hello All,
>
> This series is responsible for adding the SRAM nodes for the Wave5 VPU
> to use. The first 2 patches are responsible for carving out the SRAM
> pool from main_navss that the VPU will then reference in patches 3 and
> 4. The last 2 patches use the existing oc_sram pool already found in the
> relevant device trees.
>
> v2 properly updates the nodename in the first two patches to pass
> dtbs_check. I have talked with Andrew offline and he has said I can keep
> his reviewed-by on the first 4 patches based on v1[0].
>
The two new patches for the Sitara platforms also look good, so for the
whole series,
Acked-by: Andrew Davis <afd@ti.com>
> Best,
> Brandon
>
> [0]: https://lore.kernel.org/all/7d8582bc-e88d-40a7-be39-57045fa4c010@ti.com/
>
> Brandon Brnich (6):
> arm64: dts: ti: k3-j721s2-main: Add mmio-sram node to main_navss
> arm64: dts: ti: k3-j784s4-j742s2-main-common: Add mmio-sram node to
> main_navss
> arm64: dts: ti: k3-j721s2-main: Assign SRAM to VPU node
> arm64: dts: ti: k3-j784s4-j742s2-main-common: Assign SRAM to VPU nodes
> arm64: dts: ti: k3-am62a-main: Assign SRAM to VPU node
> arm64: dts: ti: k3-am62p-j722s-common-main: Assign SRAM to VPU node
>
> arch/arm64/boot/dts/ti/k3-am62a-main.dtsi | 1 +
> arch/arm64/boot/dts/ti/k3-am62p-j722s-common-main.dtsi | 1 +
> arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 9 +++++++++
> .../boot/dts/ti/k3-j784s4-j742s2-main-common.dtsi | 10 ++++++++++
> 4 files changed, 21 insertions(+)
>
prev parent reply other threads:[~2026-08-11 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 20:52 [PATCH v2 0/6] Add SRAM Nodes for VPU Brandon Brnich
2026-08-10 20:52 ` [PATCH v2 1/6] arm64: dts: ti: k3-j721s2-main: Add mmio-sram node to main_navss Brandon Brnich
2026-08-10 20:52 ` [PATCH v2 2/6] arm64: dts: ti: k3-j784s4-j742s2-main-common: " Brandon Brnich
2026-08-10 20:52 ` [PATCH v2 3/6] arm64: dts: ti: k3-j721s2-main: Assign SRAM to VPU node Brandon Brnich
2026-08-10 20:52 ` [PATCH v2 4/6] arm64: dts: ti: k3-j784s4-j742s2-main-common: Assign SRAM to VPU nodes Brandon Brnich
2026-08-10 20:52 ` [PATCH v2 5/6] arm64: dts: ti: k3-am62a-main: Assign SRAM to VPU node Brandon Brnich
2026-08-10 20:52 ` [PATCH v2 6/6] arm64: dts: ti: k3-am62p-j722s-common-main: " Brandon Brnich
2026-08-11 14:47 ` Andrew Davis [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=265d3c78-c7ae-4d0f-b6c0-5f9500121d86@ti.com \
--to=afd@ti.com \
--cc=b-brnich@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