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: <ceda3880-9dad-4d4a-aed5-19837a684f70@phytec.de>
Date: Mon, 19 Aug 2024 10:48:03 +0200
From: Wadim Egorov <w.egorov@...tec.de>
To: Andrew Davis <afd@...com>, Bjorn Andersson <andersson@...nel.org>, Mathieu
 Poirier <mathieu.poirier@...aro.org>, Rob Herring <robh@...nel.org>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
	Nishanth Menon <nm@...com>, Vignesh Raghavendra <vigneshr@...com>, Tero
 Kristo <kristo@...nel.org>, Philipp Zabel <p.zabel@...gutronix.de>, Hari
 Nagalla <hnagalla@...com>
CC: <linux-remoteproc@...r.kernel.org>, <devicetree@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v11 4/9] arm64: dts: ti: k3-am62: Add M4F remoteproc node



Am 02.08.24 um 17:21 schrieb Andrew Davis:
> From: Hari Nagalla <hnagalla@...com>
> 
> The AM62x SoCs of the TI K3 family have a Cortex M4F core in the MCU
> domain. This core can be used by non safety applications as a remote
> processor. When used as a remote processor with virtio/rpmessage IPC,
> two carveout reserved memory nodes are needed.
> 
> Disable by default as this node is not complete until mailbox data
> is provided in the board level DT.
> 
> Signed-off-by: Hari Nagalla <hnagalla@...com>
> Signed-off-by: Andrew Davis <afd@...com>

Tested-by: Wadim Egorov <w.egorov@...tec.de>

> ---
>   arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 13 +++++++++++++
>   1 file changed, 13 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
> index e66d486ef1f21..7f6f0007e8e81 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi
> @@ -173,4 +173,17 @@ mcu_mcan1: can@...8000 {
>   		bosch,mram-cfg = <0x0 128 64 64 64 64 32 32>;
>   		status = "disabled";
>   	};
> +
> +	mcu_m4fss: m4fss@...0000 {
> +		compatible = "ti,am64-m4fss";
> +		reg = <0x00 0x5000000 0x00 0x30000>,
> +		      <0x00 0x5040000 0x00 0x10000>;
> +		reg-names = "iram", "dram";
> +		resets = <&k3_reset 9 1>;
> +		firmware-name = "am62-mcu-m4f0_0-fw";
> +		ti,sci = <&dmsc>;
> +		ti,sci-dev-id = <9>;
> +		ti,sci-proc-ids = <0x18 0xff>;
> +		status = "disabled";
> +	};
>   };


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ