[EXTERNAL] Re: [PATCH V2 0/9] board: k3: Sync rm-cfg with TIFS v11.02.09 firmware

[Sparsh Kumar]

On 25/02/26 8:40 pm, Tom Rini wrote:
> On Wed, Feb 25, 2026 at 06:54:16PM +0530, Sparsh Kumar wrote:
> 
>> This series updates the Resource Management (RM) configuration files
>> for AM62 family devices to align with the TIFS v11.02.09 firmware.
>>
>> Background
>> ----------
>> With the latest TIFS firmware (v11.02.09), an additional virtual
>> interrupt and event is reserved for MCU cores to DM usage on am62x,
>> am62ax, and am62px devices. This series brings the rm-cfg and
>> tifs-rm-cfg files in sync with these firmware changes across both
>> TI reference boards and vendor boards.
>>
>> These changes are backward compatible with older TIFS firmware versions.
>>
>> Additionally, the am62x platform was originally introduced without a
>> tifs-rm-cfg.yaml file, unlike other platforms in the AM62 family.
>> This series addresses that gap and enables tifs-rm-cfg in binman for
>> am625-sk and am62p-sk platforms.
>>
>> Changes
>> -------
>> TI reference boards (patches 1-4):
>>    - Update rm-cfg.yaml for am62x, am62ax, am62px
>>    - Sync am62px tifs-rm-cfg.yaml with TIFS firmware template
>>    - Add missing tifs-rm-cfg.yaml for am62x
>>    - Enable tifs-rm-cfg in binman for am625-sk and am62p-sk
>>
>> Vendor boards (patches 5-9):
>>    - beagleplay (am62x-based)
>>    - phytec phycore_am62x
>>    - toradex verdin-am62
>>    - phytec phycore_am62ax
>>    - toradex verdin-am62p
>>
>> Note: For vendor boards, this series only updates the rm-cfg.yaml files
>> with the required interrupt reservation. The tifs-rm-cfg.yaml files
>> cannot be updated without access to the corresponding SysConfig files,
>> as both rm-cfg.yaml and tifs-rm-cfg.yaml must remain in sync.
> 
> Do I read this right, and the vendor boards will now be broken?
> 
Hello Tom,

No, the vendor boards will not be broken by these changes.

While it is generally recommended to keep rm-cfg.yaml and 
tifs-rm-cfg.yaml in sync, the specific changes in this series do not 
require corresponding tifs-rm-cfg.yaml updates for vendor boards:

   1. AM62ax and AM62px: The global events reservation change in 
rm-cfg.yaml has no corresponding entry in tifs-rm-cfg.yaml, so no sync 
is needed.
   2. AM62x: The virtual interrupt change would ideally need a similar 
update in tifs-rm-cfg.yaml, but none of the vendor boards have this 
file. This series introduces tifs-rm-cfg.yaml only for TI reference 
board to align with other K3 devices.

-- 
Best Regards,
Sparsh