From: Md Danish Anwar <a0501179@ti.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
MD Danish Anwar <danishanwar@ti.com>
Cc: <linux-remoteproc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<srk@ti.com>, <devicetree@vger.kernel.org>,
<netdev@vger.kernel.org>, Santosh Shilimkar <ssantosh@kernel.org>,
Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
Roger Quadros <rogerq@kernel.org>, "Andrew F. Davis" <afd@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>, Suman Anna <s-anna@ti.com>,
Bjorn Andersson <andersson@kernel.org>
Subject: Re: [PATCH v5 0/5] Introduce PRU platform consumer API
Date: Fri, 24 Mar 2023 12:43:36 +0530 [thread overview]
Message-ID: <4c9276e4-0c00-d2e9-bf9d-08cc73a75b6f@ti.com> (raw)
In-Reply-To: <20230323062451.2925996-1-danishanwar@ti.com>
Hi Mathieu,
On 23/03/23 11:54, MD Danish Anwar wrote:
> Hi All,
> The Programmable Real-Time Unit and Industrial Communication Subsystem (PRU-ICSS
> or simply PRUSS) on various TI SoCs consists of dual 32-bit RISC cores
> (Programmable Real-Time Units, or PRUs) for program execution.
>
> There are 3 foundation components for TI PRUSS subsystem: the PRUSS platform
> driver, the PRUSS INTC driver and the PRUSS remoteproc driver. All of them have
> already been merged and can be found under:
> 1) drivers/soc/ti/pruss.c
> Documentation/devicetree/bindings/soc/ti/ti,pruss.yaml
> 2) drivers/irqchip/irq-pruss-intc.c
> Documentation/devicetree/bindings/interrupt-controller/ti,pruss-intc.yaml
> 3) drivers/remoteproc/pru_rproc.c
> Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml
>
> The programmable nature of the PRUs provide flexibility to implement custom
> peripheral interfaces, fast real-time responses, or specialized data handling.
> Example of a PRU consumer drivers will be:
> - Software UART over PRUSS
> - PRU-ICSS Ethernet EMAC
>
> In order to make usage of common PRU resources and allow the consumer drivers
> to configure the PRU hardware for specific usage the PRU API is introduced.
>
Roger has given his RBs for all the patches in this series. Tony has also given
his RB.
Can you please have a look at this series.
--
Thanks and Regards,
Danish.
prev parent reply other threads:[~2023-03-24 7:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 6:24 [PATCH v5 0/5] Introduce PRU platform consumer API MD Danish Anwar
2023-03-23 6:24 ` [PATCH v5 1/5] soc: ti: pruss: Add pruss_get()/put() API MD Danish Anwar
2023-03-27 20:58 ` Mathieu Poirier
2023-03-28 5:42 ` [EXTERNAL] " Md Danish Anwar
2023-03-29 17:59 ` Mathieu Poirier
2023-03-30 9:16 ` Md Danish Anwar
2023-03-23 6:24 ` [PATCH v5 2/5] soc: ti: pruss: Add pruss_{request,release}_mem_region() API MD Danish Anwar
2023-03-27 20:59 ` Mathieu Poirier
2023-03-23 6:24 ` [PATCH v5 3/5] soc: ti: pruss: Add pruss_cfg_read()/update() API MD Danish Anwar
2023-03-23 9:30 ` Roger Quadros
2023-03-27 21:01 ` Mathieu Poirier
2023-03-28 11:17 ` [EXTERNAL] " Md Danish Anwar
2023-03-30 10:00 ` Md Danish Anwar
2023-03-30 14:21 ` Mathieu Poirier
2023-03-31 10:22 ` Md Danish Anwar
2023-03-31 11:34 ` Md Danish Anwar
2023-03-30 15:06 ` Roger Quadros
2023-03-23 6:24 ` [PATCH v5 4/5] soc: ti: pruss: Add helper functions to set GPI mode, MII_RT_event and XFR MD Danish Anwar
2023-03-23 9:32 ` Roger Quadros
2023-03-23 6:24 ` [PATCH v5 5/5] soc: ti: pruss: Add helper functions to get/set PRUSS_CFG_GPMUX MD Danish Anwar
2023-03-27 21:04 ` Mathieu Poirier
2023-03-28 11:28 ` [EXTERNAL] " Md Danish Anwar
2023-03-29 18:04 ` Mathieu Poirier
2023-03-30 9:18 ` Md Danish Anwar
2023-03-23 7:00 ` [PATCH v5 0/5] Introduce PRU platform consumer API Tony Lindgren
2023-03-24 7:13 ` Md Danish Anwar [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=4c9276e4-0c00-d2e9-bf9d-08cc73a75b6f@ti.com \
--to=a0501179@ti.com \
--cc=afd@ti.com \
--cc=andersson@kernel.org \
--cc=danishanwar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=rogerq@kernel.org \
--cc=s-anna@ti.com \
--cc=srk@ti.com \
--cc=ssantosh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).