public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Sparsh Kumar <sparsh-kumar@ti.com>
To: <trini@konsulko.com>, <u-boot@lists.denx.de>, <vigneshr@ti.com>,
	<praneeth@ti.com>, <bb@ti.com>
Cc: <afd@ti.com>, <n-francis@ti.com>, <vishalm@ti.com>,
	<sebin.francis@ti.com>, <d-gole@ti.com>, <a-kaur@ti.com>,
	Sparsh Kumar <sparsh-kumar@ti.com>
Subject: [PATCH V2 7/9] toradex: verdin-am62: rm-cfg: Update rm-cfg to reflect new resource reservation
Date: Wed, 25 Feb 2026 18:54:23 +0530	[thread overview]
Message-ID: <20260225132425.3096103-8-sparsh-kumar@ti.com> (raw)
In-Reply-To: <20260225132425.3096103-1-sparsh-kumar@ti.com>

With the latest v11.02.09 TIFS firmware, an additional
virtual interrupt and event is reserved for MCU cores
to DM usage on am62x devices.

Update the rm-cfg to reflect this new reservation.

Signed-off-by: Sparsh Kumar <sparsh-kumar@ti.com>
---
 board/toradex/verdin-am62/rm-cfg.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/board/toradex/verdin-am62/rm-cfg.yaml b/board/toradex/verdin-am62/rm-cfg.yaml
index ea5f2423cf3..8204031449e 100644
--- a/board/toradex/verdin-am62/rm-cfg.yaml
+++ b/board/toradex/verdin-am62/rm-cfg.yaml
@@ -525,7 +525,7 @@ rm-cfg:
             reserved: 0
         -
             start_resource: 168
-            num_resource: 8
+            num_resource: 7
             type: 1802
             host_id: 30
             reserved: 0
@@ -555,7 +555,7 @@ rm-cfg:
             reserved: 0
         -
             start_resource: 909
-            num_resource: 626
+            num_resource: 625
             type: 1805
             host_id: 128
             reserved: 0
-- 
2.34.1


  parent reply	other threads:[~2026-02-25 14:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 13:24 [PATCH V2 0/9] board: k3: Sync rm-cfg with TIFS v11.02.09 firmware Sparsh Kumar
2026-02-25 13:24 ` [PATCH V2 1/9] board: ti: rm-cfg: Update rm-cfg to reflect new resource reservation Sparsh Kumar
2026-02-25 13:24 ` [PATCH V2 2/9] board: ti: am62px: tifs-rm-cfg: Sync tifs-rm-cfg with TIFS firmware updates Sparsh Kumar
2026-02-25 13:24 ` [PATCH V2 3/4] board: ti: am62x: tifs-rm-cfg: Add the missing tifs-rm-cfg: Sparsh Kumar
2026-02-25 13:24 ` [PATCH V2 4/4] arm: dts: k3: am62x/am62px: Enable tifs-rm-cfg in binman Sparsh Kumar
2026-02-27 10:05   ` Francis, Neha
2026-02-25 13:24 ` [PATCH V2 5/9] board: beagle: beagleplay: rm-cfg: Update rm-cfg to reflect new resource reservation Sparsh Kumar
2026-02-25 13:24 ` [PATCH V2 6/9] board: phytec: " Sparsh Kumar
2026-02-25 13:24 ` Sparsh Kumar [this message]
2026-02-25 13:24 ` [PATCH V2 8/9] board: phytec: phycore_am62ax: " Sparsh Kumar
2026-02-25 13:24 ` [PATCH V2 9/9] board: toradex: verdin-am62p: " Sparsh Kumar
2026-02-25 15:10 ` [PATCH V2 0/9] board: k3: Sync rm-cfg with TIFS v11.02.09 firmware Tom Rini
2026-02-25 15:47   ` [EXTERNAL] " Sparsh Kumar
2026-03-13 23:39 ` Tom Rini

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=20260225132425.3096103-8-sparsh-kumar@ti.com \
    --to=sparsh-kumar@ti.com \
    --cc=a-kaur@ti.com \
    --cc=afd@ti.com \
    --cc=bb@ti.com \
    --cc=d-gole@ti.com \
    --cc=n-francis@ti.com \
    --cc=praneeth@ti.com \
    --cc=sebin.francis@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=vigneshr@ti.com \
    --cc=vishalm@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