linux-kernel - Re: [PATCH v3 17/33] arm64: dts: ti: k3-am642-sr-som: Add missing cfg for TI IPC Firmware

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250905063449.GA6194@francesco-nb>
Date: Fri, 5 Sep 2025 08:34:49 +0200
From: Francesco Dolcini <francesco@...cini.it>
To: Beleswar Padhi <b-padhi@...com>
Cc: nm@...com, vigneshr@...com, kristo@...nel.org, robh@...nel.org,
	krzk+dt@...nel.org, conor+dt@...nel.org, afd@...com,
	u-kumar1@...com, hnagalla@...com, jm@...com,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	Josua Mayer <josua@...id-run.com>,
	Logan Bristol <logan.bristol@...xas.edu>,
	Matthias Schiffer <matthias.schiffer@...tq-group.com>
Subject: Re: [PATCH v3 17/33] arm64: dts: ti: k3-am642-sr-som: Add missing
 cfg for TI IPC Firmware

On Fri, Sep 05, 2025 at 10:48:30AM +0530, Beleswar Padhi wrote:
> Currently, only R5F remote processors are enabled for k3-am642-sr SoMs,
> whereas the M4F in MCU domain is disabled. Enable the M4F remote
> processor at board level by reserving memory carveouts and assigning
> mailboxes.
> 
> While at it, reserve the MAIN domain timers that are used by R5F remote
> processors for ticks to avoid rproc crashes. This config aligns with
> other AM64 boards and can be refactored out later.
> 
> Signed-off-by: Beleswar Padhi <b-padhi@...com>
> ---
> Cc: Josua Mayer <josua@...id-run.com>
> Cc: Logan Bristol <logan.bristol@...xas.edu>
> Cc: Matthias Schiffer <matthias.schiffer@...tq-group.com>
> Requesting for review/test of this patch.
> 
> v3: Changelog:
> 1. None
> 
> Link to v2:
> https://lore.kernel.org/all/20250823160901.2177841-18-b-padhi@ti.com/
> 
> v2: Changelog:
> 1. Re-ordered patch from [PATCH 27/33] to [PATCH v2 17/33].
> 
> Link to v1:
> https://lore.kernel.org/all/20250814223839.3256046-28-b-padhi@ti.com/
> 
>  arch/arm64/boot/dts/ti/k3-am642-sr-som.dtsi | 54 +++++++++++++++++++++
>  1 file changed, 54 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/ti/k3-am642-sr-som.dtsi b/arch/arm64/boot/dts/ti/k3-am642-sr-som.dtsi
> index 81adae0a8e55..8cb61f831734 100644
> --- a/arch/arm64/boot/dts/ti/k3-am642-sr-som.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am642-sr-som.dtsi
> @@ -162,6 +162,24 @@ main_r5fss1_core1_memory_region: r5f-memory@...00000 {
>  			reg = <0x00 0xa3100000 0x00 0xf00000>;
>  			no-map;
>  		};
> +
> +		mcu_m4fss_dma_memory_region: m4f-dma-memory@...00000 {

this must be

mcu_m4fss_dma_memory_region: memory@...00000

the device tree specification requires generic node names, my comment [1]
had nothing specific on verdin am62/am62p.

Francesco

[1] https://lore.kernel.org/all/20250821060629.GB7503@francesco-nb/