Introduce PRU remoteproc consumer API
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v5 Latest6 patches 17 repliesIn review
- v46 patches 4 repliesSuperseded
- v35 patches 7 repliesSuperseded
Earlier versions · 1
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v1 RFC | 13 patches | 15 replies | Superseded |
Patches in v5 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | dt-bindings: remoteproc: Add PRU consumer bindingsDocumentation/ | +69 | 1 reply | |
| 2/6 | remoteproc: pru: Add APIs to get and put the PRU coresdrivers/ include/ | +189 | 11 replies | |
| 3/6 | remoteproc: pru: Make sysfs entries read-only for PRU client driven bootsdrivers/ | +2 | 0 replies | |
| 4/6 | remoteproc: pru: Add pru_rproc_set_ctable() functiondrivers/ include/ | +81 | 1 reply | |
| 5/6 | remoteproc: pru: Configure firmware based on client setupdrivers/ | +35 | 0 replies | |
| 6/6 | remoteproc: pru: add support for configuring GPMUX based on client setupdrivers/ | +20 | 4 replies |
Reviews trailers per patch
1 of 6 patches has a Reviewed-by or Acked-by.
| Patch | Rob Herring |
|---|---|
| 1/6 | R-b |
| 2/6 | |
| 3/6 | |
| 4/6 | |
| 5/6 | |
| 6/6 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v5 0/6] Introduce PRU remoteproc consumer API
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/[email protected]/
[2] https://patchwork.kernel.org/project/linux-remoteproc/cover/[email protected]/
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
Signature · 1 line
2.17.1