devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Puranjay Mohan <p-mohan@ti.com>
To: <linux-kernel@vger.kernel.org>
Cc: <bjorn.andersson@linaro.org>, <mathieu.poirier@linaro.org>,
	<krzysztof.kozlowski+dt@linaro.org>,
	<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<nm@ti.com>, <ssantosh@kernel.org>, <s-anna@ti.com>,
	<p-mohan@ti.com>, <linux-arm-kernel@lists.infradead.org>,
	<rogerq@kernel.org>, <grygorii.strashko@ti.com>,
	<vigneshr@ti.com>, <kishon@ti.com>, <robh@kernel.org>
Subject: [PATCH v5 0/6] Introduce PRU remoteproc consumer API
Date: Tue, 7 Jun 2022 10:26:44 +0530	[thread overview]
Message-ID: <20220607045650.4999-1-p-mohan@ti.com> (raw)

This is the v5 of the patch series [1]. The 6th patch in the series was
added in v4 and it had some checkpatch.pl errors which are removed here.

I have posted two more patch series that depend on this series, one to
the soc tree and another to the networking tree. I had sent all the 3
series, including this one as RFC [2] to get comments and to explain the
dependencies.

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 PRUSS subsystem: the PRUSS platform
driver, the PRUSS INTC driver and the PRUSS remoteproc driver. All were
already 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-rproc.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.

[1] https://patchwork.kernel.org/project/linux-remoteproc/cover/20220603121520.13730-1-p-mohan@ti.com/
[2] https://patchwork.kernel.org/project/linux-remoteproc/cover/20220406094358.7895-1-p-mohan@ti.com/

Thanks and Regards,
Puranjay Mohan

Roger Quadros (1):
  remoteproc: pru: Add pru_rproc_set_ctable() function

Suman Anna (2):
  dt-bindings: remoteproc: Add PRU consumer bindings
  remoteproc: pru: Make sysfs entries read-only for PRU client driven
    boots

Tero Kristo (3):
  remoteproc: pru: Add APIs to get and put the PRU cores
  remoteproc: pru: Configure firmware based on client setup
  remoteproc: pru: add support for configuring GPMUX based on client
    setup

 .../bindings/remoteproc/ti,pru-consumer.yaml  |  69 +++++
 drivers/remoteproc/pru_rproc.c                | 254 +++++++++++++++++-
 include/linux/pruss.h                         |  78 ++++++
 3 files changed, 396 insertions(+), 5 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml
 create mode 100644 include/linux/pruss.h

-- 
2.17.1


             reply	other threads:[~2022-06-07  4:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07  4:56 Puranjay Mohan [this message]
2022-06-07  4:56 ` [PATCH v5 1/6] dt-bindings: remoteproc: Add PRU consumer bindings Puranjay Mohan
2022-07-19 16:17   ` Mathieu Poirier
2022-06-07  4:56 ` [PATCH v5 2/6] remoteproc: pru: Add APIs to get and put the PRU cores Puranjay Mohan
2022-07-12 17:59   ` Mathieu Poirier
2022-07-14 17:20     ` Mathieu Poirier
2022-07-15  6:22       ` Kishon Vijay Abraham I
2022-09-02  9:39         ` Md Danish Anwar
2022-09-06 19:28           ` Mathieu Poirier
2022-09-07  9:24             ` Md Danish Anwar
2022-09-12 13:24               ` Romain Naour
2022-09-13 11:40                 ` Md Danish Anwar
2022-09-19 20:45                   ` Mathieu Poirier
2022-09-26 10:23                     ` [EXTERNAL] " Md Danish Anwar
2022-09-29 23:02                       ` Mathieu Poirier
2022-06-07  4:56 ` [PATCH v5 3/6] remoteproc: pru: Make sysfs entries read-only for PRU client driven boots Puranjay Mohan
2022-06-07  4:56 ` [PATCH v5 4/6] remoteproc: pru: Add pru_rproc_set_ctable() function Puranjay Mohan
2022-07-19 15:53   ` Mathieu Poirier
2022-06-07  4:56 ` [PATCH v5 5/6] remoteproc: pru: Configure firmware based on client setup Puranjay Mohan
2022-06-07  4:56 ` [PATCH v5 6/6] remoteproc: pru: add support for configuring GPMUX " Puranjay Mohan
2022-07-19 16:16   ` Mathieu Poirier
2022-09-05  9:11     ` Md Danish Anwar
2022-09-06 19:29       ` Mathieu Poirier
2022-09-07  9:14         ` [EXTERNAL] " Md Danish Anwar

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=20220607045650.4999-1-p-mohan@ti.com \
    --to=p-mohan@ti.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grygorii.strashko@ti.com \
    --cc=kishon@ti.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=nm@ti.com \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=s-anna@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).