linux-kernel - Re: [PATCH v2 00/33] Refactor TI IPC DT configs into dtsi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5dc272a9-6a14-47df-e7ce-006517e2cb43@ti.com>
Date: Thu, 4 Sep 2025 21:44:54 -0500
From: Hari Nagalla <hnagalla@...com>
To: Judith Mendez <jm@...com>, Beleswar Padhi <b-padhi@...com>, <nm@...com>,
        <vigneshr@...com>, <kristo@...nel.org>, <robh@...nel.org>,
        <krzk+dt@...nel.org>, <conor+dt@...nel.org>
CC: <afd@...com>, <u-kumar1@...com>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
        Robert Nelson <robertcnelson@...il.com>,
        Jo_o Paulo Gon_alves
	<joao.goncalves@...adex.com>,
        Parth Pancholi <parth.pancholi@...adex.com>,
        Emanuele Ghidoli <emanuele.ghidoli@...adex.com>,
        Francesco Dolcini
	<francesco.dolcini@...adex.com>,
        Matthias Schiffer
	<matthias.schiffer@...tq-group.com>,
        Logan Bristol
	<logan.bristol@...xas.edu>,
        Josua Mayer <josua@...id-run.com>, John Ma
	<jma@...tec.com>,
        Nathan Morrisson <nmorrisson@...tec.com>,
        Garrett Giordano
	<ggiordano@...tec.com>,
        Matt McKee <mmckee@...tec.com>, Wadim Egorov
	<w.egorov@...tec.de>,
        Andrejs Cainikovs <andrejs.cainikovs@...adex.com>,
        "Max
 Krummenacher" <max.krummenacher@...adex.com>,
        Stefan Eichenberger
	<stefan.eichenberger@...adex.com>,
        Hiago De Franco <hiago.franco@...adex.com>
Subject: Re: [PATCH v2 00/33] Refactor TI IPC DT configs into dtsi

On 9/4/25 15:40, Judith Mendez wrote:
> Hi Beleswar,
> 
> On 8/23/25 11:08 AM, Beleswar Padhi wrote:
>> The TI K3 SoCs have multiple programmable remote processors like
>> R5F, M4F, C6x/C7x etc. The TI SDKs for these SoCs offer sample firmware
>> which could be run on these cores to demonstrate an "echo" IPC test.
>> Those firmware require certain memory carveouts to be reserved from
>> system memory, timers to be reserved, and certain mailbox
>> configurations for interrupt based messaging. These configurations
>> could be different for a different firmware.
>>
>> Refactor these firmware dependent configurations from board level DTS
>> into a dtsi for now. This dtsi for TI IPC firmware is board-independent
>> and can be applied to all boards from the same SoC Family. This gets
>> rid of code duplication (>50%) and allows more freedom for users
>> developing custom firmware (or no firmware) to utilize system resources
>> better; easily by swapping out this dtsi. To maintain backward
>> compatibility, the dtsi is included in all existing boards.
>>
>> DTSI vs Overlay:
>> 1. I chose DTSI over overlay as both the ways required including the
>> refactored file in existing board-level files to maintain backward
>> compatibility, so didn't see the advantage of using overlays here.
>> 2. If we do down the overlay path, existing board-level file names have
>> to be changed to indicate they are without the IPC support; so that
>> they can be combined with the overlay to generate the same-named DTBs.
>> For example:
>> k3-am69-sk.dtb := k3-am69-sk-sans-ipc.dtb k3-j784s4-ti-ipc-firmware.dtbo
>>                  ~~~~~~~~
>>
>> I am not sure if this renaming of files is ideal?
>>
> 
> Thanks for you patches, I was able to boot test on am62px SK and
> am62ax SK boards. I was also able do a simple rpmsg echo test with some
> additional patches on top of your changes:
> https://gist.github.com/jmenti/4ae7a6a65c2cb95fd54f48d32430c1e9
> 
> so for am62ax and am62px SK boards:
> 
> Tested-by: Judith Mendez <jm@...com>
>
Tested the AM64 dts patches on AM64-SK board and it worked.
Thanks

Tested-by: Hari Nagalla <hnagalla@...com>