From: Ravi Gunasekaran <r-gunasekaran@ti.com>
To: MD Danish Anwar <danishanwar@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>, Nishanth Menon <nm@ti.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Tero Kristo <kristo@kernel.org>, <srk@ti.com>,
Roger Quadros <rogerq@kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am64-main: Add PRU system events for virtio
Date: Wed, 24 Apr 2024 12:25:24 +0530 [thread overview]
Message-ID: <3f00114c-7185-4a50-9d6a-b3e31d7d3eb5@ti.com> (raw)
In-Reply-To: <20240423100608.1421652-1-danishanwar@ti.com>
On 4/23/2024 3:36 PM, MD Danish Anwar wrote:
> From: Suman Anna <s-anna@ti.com>
>
> PRU system events "vring" have been added to each PRU and RTU node
> in each of the ICSSG0 and ICSSG1 remote processor subsystems to
> enable the virtio/rpmsg communication between MPU and that PRU/RTU core.
> No events have been added to the Tx_PRU cores at present. The
> additions are done in the base k3-am64main.dtsi, and so are inherited
> by all the K3 AM64x 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@ti.com>
> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
> Signed-off-by: MD Danish Anwar <danishanwar@ti.com>
> ---
> This patch is based on linux-next tag next-20240423
>
> arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
>
Acked-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
Regards,
Ravi
prev parent reply other threads:[~2024-04-24 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 10:06 MD Danish Anwar
2024-04-24 6:55 ` Ravi Gunasekaran [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f00114c-7185-4a50-9d6a-b3e31d7d3eb5@ti.com \
--to=r-gunasekaran@ti.com \
--cc=conor+dt@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=rogerq@kernel.org \
--cc=srk@ti.com \
--cc=vigneshr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®