From: Judith Mendez <jm@ti.com>
To: <linux-omap@vger.kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Tony Lindgren" <tony@atomide.com>,
"Rob Herring" <robh@kernel.org>,
"Benoît Cousson" <bcousson@baylibre.com>
Subject: Re: [PATCH] ARM: dts: am335x: Add PRU system events for virtio
Date: Mon, 6 May 2024 17:09:33 -0500 [thread overview]
Message-ID: <8651bce3-d097-465d-b8a7-c12e9d8a77b1@ti.com> (raw)
In-Reply-To: <20240501194157.2727136-1-jm@ti.com>
Hi all,
On 5/1/24 2:41 PM, Judith Mendez wrote:
> From: Nick Saulnier <nsaulnier@ti.com>
>
> A PRU system event "vring" has been added to each of the PRU nodes in
> the PRU-ICSS remote processor subsystem to enable the virtio/rpmsg
> communication between MPU and that PRU core. The additions are done
> in the base am33xx-l4.dtsi, and so are inherited by all the AM335x
> boards. Do note that PRUSS is available only on all AM3356+ SoCs.
>
> The PRU system events is the preferred approach over using OMAP
> mailboxes, as it eliminates an external peripheral access from
> the PRU-side, and keeps the interrupt generation internal to the
> PRUSS. 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 the SoC to use mailboxes. Either approach
> would require that an appropriate firmware image is loaded/booted on
> the PRU.
Please ignore this patch,
Thanks,
Judith
prev parent reply other threads:[~2024-05-06 22:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 19:41 [PATCH] ARM: dts: am335x: Add PRU system events for virtio Judith Mendez
2024-05-06 22:09 ` Judith Mendez [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=8651bce3-d097-465d-b8a7-c12e9d8a77b1@ti.com \
--to=jm@ti.com \
--cc=bcousson@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tony@atomide.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