board: beagle: beagleplay: rm-cfg: resync with am62x
PATCH 1/1 board: beagle: beagleplay: rm-cfg: resync with am62x
From: Randolph Sapp <[email protected]>
Apparently this wasn't being kept in sync properly. Commit 2a64978fa89a ("board: beagle: beagleplay: rm-cfg: Update rm-cfg to reflect new resource reservation"), which was supposed to be equivalent to 7f9c2a6f7be7 ("board: ti: rm-cfg: Update rm-cfg to reflect new resource reservation") was subtly different to work around this.
This file was missing the following commits:
87720385ab69 ("board: ti: rm-cfg: Update rm-cfg to reflect new resource reservation") ef756f1bcd2c ("board: ti: am62x/am62ax: Update MCU GPIO interrupt allocation in board config")
---
The am62px/beagley-ai only has one old entry. The j721e/beagleboneai64 diff though. That's a nightmare. I'll look at those a little more before submitting them. Boot testing everything.
board/beagle/beagleplay/rm-cfg.yaml | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-)
board/beagle/beagleplay/rm-cfg.yaml +19 -7
@@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0+ -# Copyright (C) 2022-2023 Texas Instruments Incorporated - https://www.ti.com/ +# Copyright (C) 2022-2026 Texas Instruments Incorporated - https://www.ti.com/ # -# Resource management configuration for AM62 +# Resource management configuration for AM62X # ---
@@ -244,7 +244,7 @@ rm-cfg: subhdr: magic: 0x7B25 size: 8 - resasg_entries_size: 960 + resasg_entries_size: 976 reserved: 0 resasg_entries: -
@@ -285,10 +285,22 @@ rm-cfg: reserved: 0 - start_resource: 0 - num_resource: 4 + num_resource: 2 type: 320 host_id: 12 reserved: 0 + - + start_resource: 2 + num_resource: 2 + type: 320 + host_id: 35 + reserved: 0 + - + start_resource: 2 + num_resource: 2 + type: 320 + host_id: 36 + reserved: 0 - start_resource: 4 num_resource: 4
@@ -501,13 +513,13 @@ rm-cfg: reserved: 0 - start_resource: 44 - num_resource: 36 + num_resource: 35 type: 1802 host_id: 35 reserved: 0 - start_resource: 44 - num_resource: 36 + num_resource: 35 type: 1802 host_id: 36 reserved: 0
@@ -543,7 +555,7 @@ rm-cfg: reserved: 0 - start_resource: 909 - num_resource: 626 + num_resource: 625 type: 1805 host_id: 128 reserved: 0
Signature · 1 line
2.55.0
Quoted 9 lines · On Thu, 30 Jul 2026 18:13:40 -0500, [email protected] wrote:
Apparently this wasn't being kept in sync properly. Commit
2a64978fa89a("board: beagle: beagleplay: rm-cfg: Update rm-cfg to reflect new resource reservation"), which was supposed to be equivalent to7f9c2a6f7be7("board: ti: rm-cfg: Update rm-cfg to reflect new resource reservation") was subtly different to work around this.This file was missing the following commits:
[...]
Applied to u-boot/next, thanks!
[1/1] board: beagle: beagleplay: rm-cfg: resync with am62x
commit: 8841b7b292c74864acf4ed0bd8ce05839252c1f2
Signature · 1 line
Tom