From: MD Danish Anwar <danishanwar@ti.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: Suman Anna <s-anna@ti.com>, Roger Quadros <rogerq@kernel.org>,
"Andrew F . Davis" <afd@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<srk@ti.com>, <linux-remoteproc@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
MD Danish Anwar <danishanwar@ti.com>
Subject: [PATCH v8 0/6] Introduce PRU remoteproc consumer API
Date: Wed, 16 Nov 2022 17:46:28 +0530 [thread overview]
Message-ID: <20221116121634.2901265-1-danishanwar@ti.com> (raw)
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.
This is the v8 of the patch series [1]. This version of the patchset
addresses the comments made on v7 [7] of the series.
Two more patch series have been posted ([2] and [3]) that depends on this
series, one has been posted to the soc/ti/ tree and another
to the networking tree. All the 3 series including this one, has been
sent as RFC [4] to get comments and to explain the dependencies.
Changes from v7 to v8 :
*) Removed get_device(&rproc->dev) from API __pru_rproc_get() in patch 2/5 of
this series as asked by Roger.
*) Replaced all the SoBs (other than mine) to Co-developed-by tags for all
the patches in this series as asked by Mathieu.
*) Added a new patch (3/5) in this series for Introduction of pruss_pru_id enum.
Previously this enum was part of patch 2/5. As asked by Roger removed this enum
(and the APIs that are using the enum) from patch 2/5 and added it in new patch.
*) Removed a comment for an already documented field in patch 2/5 of this series.
*) Changed 'pru' to 'PRU' in comment of API pru_rproc_set_firmware() as asked by
Roger.
Changes from v6 [6] to v7 :
*) Removed example section from ti,pru-consumer.yaml as the full example
included compatible property as well which is not introduced in this series
thus creating dt check binding error. Removing the example section fixes the
dt binding check error. The example section will be included in
"ti,icssg-prueth.yaml" in the next version of series [3]
*) Updated the commit message for patch 1/5 of this series to address Krzysztof's
comment.
Changes from v5 [5] to v6 :
*) Added rproc_get_by_phandle() in pru_rproc_get()
*) Provided background of Ctable in the commit messege.
*) Removed patch "" [8] (6th Patch of the previous version of this series)
as it has dependency on series [2], thus creating a cyclic dependency.
The patch [6] will be sent along with the next version of series [2].
[1] https://patchwork.kernel.org/project/linux-remoteproc/cover/20220603121520.13730-1-p-mohan@ti.com/
[2] https://lore.kernel.org/all/20220418123004.9332-1-p-mohan@ti.com/
[3] https://lore.kernel.org/all/20220531095108.21757-1-p-mohan@ti.com/
[4] https://patchwork.kernel.org/project/linux-remoteproc/cover/20220406094358.7895-1-p-mohan@ti.com/
[5] https://lore.kernel.org/all/20220607045650.4999-1-p-mohan@ti.com/
[6] https://lore.kernel.org/all/20221012114429.2341215-1-danishanwar@ti.com/
[7] https://lore.kernel.org/all/20221031073801.130541-1-danishanwar@ti.com/
[8] https://lore.kernel.org/all/20220607045650.4999-7-p-mohan@ti.com/
Thanks and Regards,
Md Danish Anwar
MD Danish Anwar (1):
remoteproc: pru: Add enum for PRU Core Indentifiers.
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 (2):
remoteproc: pru: Add APIs to get and put the PRU cores
remoteproc: pru: Configure firmware based on client setup
.../bindings/remoteproc/ti,pru-consumer.yaml | 60 +++++
drivers/remoteproc/pru_rproc.c | 235 +++++++++++++++++-
include/linux/pruss.h | 78 ++++++
3 files changed, 368 insertions(+), 5 deletions(-)
create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,pru-consumer.yaml
create mode 100644 include/linux/pruss.h
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-11-16 12:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 12:16 MD Danish Anwar [this message]
2022-11-16 12:16 ` [PATCH v8 1/6] dt-bindings: remoteproc: Add PRU consumer bindings MD Danish Anwar
2022-11-16 16:09 ` Rob Herring
2022-11-16 18:09 ` Mathieu Poirier
2022-11-18 5:48 ` [EXTERNAL] " Md Danish Anwar
2022-11-18 18:56 ` Mathieu Poirier
2022-11-16 12:16 ` [PATCH v8 2/6] remoteproc: pru: Add APIs to get and put the PRU cores MD Danish Anwar
2022-11-16 12:16 ` [PATCH v8 3/6] remoteproc: pru: Add enum for PRU Core Indentifiers MD Danish Anwar
2022-11-16 12:16 ` [PATCH v8 4/6] remoteproc: pru: Make sysfs entries read-only for PRU client driven boots MD Danish Anwar
2022-11-16 12:16 ` [PATCH v8 5/6] remoteproc: pru: Add pru_rproc_set_ctable() function MD Danish Anwar
2022-11-16 12:16 ` [PATCH v8 6/6] remoteproc: pru: Configure firmware based on client setup 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=20221116121634.2901265-1-danishanwar@ti.com \
--to=danishanwar@ti.com \
--cc=afd@ti.com \
--cc=devicetree@vger.kernel.org \
--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+dt@kernel.org \
--cc=rogerq@kernel.org \
--cc=s-anna@ti.com \
--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