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: <0b572ad3-800b-4d62-8ddc-2207a82a2f41@ti.com>
Date: Wed, 24 Apr 2024 12:28:30 +0530
From: Ravi Gunasekaran <r-gunasekaran@...com>
To: MD Danish Anwar <danishanwar@...com>,
        Vignesh Raghavendra
	<vigneshr@...com>, Nishanth Menon <nm@...com>
CC: Conor Dooley <conor+dt@...nel.org>,
        Krzysztof Kozlowski
	<krzk+dt@...nel.org>,
        Rob Herring <robh@...nel.org>, <linux-kernel@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
        Tero Kristo <kristo@...nel.org>, <srk@...com>,
        Roger Quadros <rogerq@...nel.org>, <srk@...com>,
        Ravi
 Gunasekaran <r-gunasekaran@...com>
Subject: Re: [PATCH] arm64: dts: ti: k3-am65-main: Add PRU system events for
 virtio



On 4/23/2024 3:38 PM, MD Danish Anwar wrote:
> From: Suman Anna <s-anna@...com>
>
> A PRU system event "vring" has been added to each PRU and RTU
> node in each of the ICSSG0, ICSSG1 and ICSSG2 remote processor
> subsystems to enable the virtio/rpmsg communication between MPU
> and that PRU/RTU core. The additions are done in the base
> k3-am65-main.dtsi, and so are inherited by all the K3 AM65x
> boards.
>
> The PRU system events is the preferred approach over using TI
> mailboxes, as it eliminates an external peripheral access from
> the PRU/RTU-side, and keeps the interrupt generation internal to
> the ICSSG. The difference from MPU would be minimal in using one
> versus the other.
>
> Mailboxes can still be used if desired, but currently there is
> no support on firmware-side for K3 SoCs to use mailboxes. Either
> approach would require that an appropriate firmware image is
> loaded/booted on the PRU.
>
> Signed-off-by: Suman Anna <s-anna@...com>
> Signed-off-by: Kishon Vijay Abraham I <kishon@...com>
> Signed-off-by: MD Danish Anwar <danishanwar@...com>
> ---
> This patch is based on linux-next tag next-20240423
>
>  arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 36 ++++++++++++++++++++++++
>  1 file changed, 36 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
> index 0d68aa8e946f..72aa3b9aacce 100644
> --- a/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am65-main.dtsi
>

Acked-by: Ravi Gunasekaran <r-gunasekaran@...com>

Regards,
Ravi

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ