From: Roger Quadros <rogerq@ti.com> To: ohad@wizery.com, bjorn.andersson@linaro.org Cc: tony@atomide.com, robh+dt@kernel.org, bcousson@baylibre.com, ssantosh@kernel.org, s-anna@ti.com, nsekhar@ti.com, t-kristo@ti.com, nsaulnier@ti.com, jreeder@ti.com, m-karicheri2@ti.com, woods.technical@gmail.com, linux-omap@vger.kernel.org, linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, rogerq@ti.com Subject: [PATCH 00/16] remoteproc: Add support for TI PRU Date: Mon, 26 Nov 2018 09:52:33 +0200 [thread overview] Message-ID: <1543218769-5507-1-git-send-email-rogerq@ti.com> (raw) Hi, This is the second part of the series [1] and depends on it. It adds remoteproc support for the PRU processor cores present in the PRU-ICSS subsystem on TI SoCs. The PRU remoteproc driver uses the standard remoteproc core ELF loader. However, the PRUs do not have a unified address space, (has an Instruction RAM and a primary Data RAM at both 0x0) and leverage an added .da_to_va ops to use the standard ELF loader. This remoteproc driver does not have support for error recovery and system suspend/resume features. Different compatibles are used to allow providing scalability for instance-specific device data if needed. The driver uses a default firmware-name retrieved from device-tree, and the firmwares are expected to be present in the standard Linux firmware search paths. They can also be adjusted by userspace if required through the sysfs interface provided by the remoteproc core. The PRU remoteproc driver uses a client-driven boot methodology - it does _not_ support auto-boot so that the PRU load and boot is dictated by the corresponding client drivers for achieving various usecases. This allows flexibility for the client drivers or applications to set a firmware name (if needed) based on their desired functionality and boot the PRU. Finally it adds some helper APIs for client drivers to set PRU specific settings .e.g Constant Table, GPI mode, etc. Testing: To test the code with example firmware you can try the LAB5 tutorial http://processors.wiki.ti.com/index.php/PRU_Training:_Hands-on_Labs#LAB_5:_RPMsg_Communication_between_ARM_and_PRU with the pru-software-support package at [2] and the sample rpmsg-client driver. NOTE: you no longer need to build and run PRU_Halt example as shown in the tutorial. cheers, -roger [1] https://lkml.org/lkml/2018/11/22/948 [2] https://github.com/rogerq/pru-software-support-package/commits/upstream/pruss Roger Quadros (2): remoteproc/pru: Add pru_rproc_set_ctable() function remoteproc/pru: Add support for INTC Interrupt map resource Suman Anna (9): remoteproc: Extend rproc_da_to_va() API with a flags parameter remoteproc: Add a rproc_set_firmware() API remoteproc: Add support to handle device specific resource types remoteproc/pru: Add PRU remoteproc driver remoteproc/pru: Add pru-specific debugfs support dt-bindings: remoteproc: ti-pruss: Update bindings for supporting rpmsg remoteproc/pru: Add support for virtio rpmsg stack remoteproc/pru: add pru_rproc_get_id() API to retrieve the PRU id soc: ti: pruss: add helper functions to set GPI mode, MII_RT_event and XFR Tero Kristo (5): remoteproc/pru: add APIs to get and put the PRU cores dt-bindings: remoteproc: ti-pruss: Document application node bindings remoteproc/pru: add support for configuring GPMUX based on client setup remoteproc/pru: configure firmware based on client setup remoteproc/pru: add support for parsing pru interrupt mapping from DT .../devicetree/bindings/soc/ti/ti,pruss.txt | 82 ++ drivers/remoteproc/Kconfig | 16 + drivers/remoteproc/Makefile | 1 + drivers/remoteproc/imx_rproc.c | 2 +- drivers/remoteproc/keystone_remoteproc.c | 3 +- drivers/remoteproc/pru_rproc.c | 1138 ++++++++++++++++++++ drivers/remoteproc/pru_rproc.h | 55 + drivers/remoteproc/qcom_q6v5_mss.c | 5 +- drivers/remoteproc/qcom_q6v5_pas.c | 2 +- drivers/remoteproc/qcom_q6v5_wcss.c | 2 +- drivers/remoteproc/qcom_wcnss.c | 2 +- drivers/remoteproc/remoteproc_core.c | 112 +- drivers/remoteproc/remoteproc_debugfs.c | 3 + drivers/remoteproc/remoteproc_elf_loader.c | 6 +- drivers/remoteproc/remoteproc_internal.h | 2 +- drivers/remoteproc/remoteproc_sysfs.c | 33 +- drivers/remoteproc/st_slim_rproc.c | 3 +- drivers/remoteproc/wkup_m3_rproc.c | 3 +- include/linux/pruss.h | 168 +++ include/linux/remoteproc.h | 32 +- 20 files changed, 1620 insertions(+), 50 deletions(-) create mode 100644 drivers/remoteproc/pru_rproc.c create mode 100644 drivers/remoteproc/pru_rproc.h -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
WARNING: multiple messages have this Message-ID (diff)
From: Roger Quadros <rogerq@ti.com> To: <ohad@wizery.com>, <bjorn.andersson@linaro.org> Cc: <tony@atomide.com>, <robh+dt@kernel.org>, <bcousson@baylibre.com>, <ssantosh@kernel.org>, <s-anna@ti.com>, <nsekhar@ti.com>, <t-kristo@ti.com>, <nsaulnier@ti.com>, <jreeder@ti.com>, <m-karicheri2@ti.com>, <woods.technical@gmail.com>, <linux-omap@vger.kernel.org>, <linux-remoteproc@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>, <rogerq@ti.com> Subject: [PATCH 00/16] remoteproc: Add support for TI PRU Date: Mon, 26 Nov 2018 09:52:33 +0200 [thread overview] Message-ID: <1543218769-5507-1-git-send-email-rogerq@ti.com> (raw) Hi, This is the second part of the series [1] and depends on it. It adds remoteproc support for the PRU processor cores present in the PRU-ICSS subsystem on TI SoCs. The PRU remoteproc driver uses the standard remoteproc core ELF loader. However, the PRUs do not have a unified address space, (has an Instruction RAM and a primary Data RAM at both 0x0) and leverage an added .da_to_va ops to use the standard ELF loader. This remoteproc driver does not have support for error recovery and system suspend/resume features. Different compatibles are used to allow providing scalability for instance-specific device data if needed. The driver uses a default firmware-name retrieved from device-tree, and the firmwares are expected to be present in the standard Linux firmware search paths. They can also be adjusted by userspace if required through the sysfs interface provided by the remoteproc core. The PRU remoteproc driver uses a client-driven boot methodology - it does _not_ support auto-boot so that the PRU load and boot is dictated by the corresponding client drivers for achieving various usecases. This allows flexibility for the client drivers or applications to set a firmware name (if needed) based on their desired functionality and boot the PRU. Finally it adds some helper APIs for client drivers to set PRU specific settings .e.g Constant Table, GPI mode, etc. Testing: To test the code with example firmware you can try the LAB5 tutorial http://processors.wiki.ti.com/index.php/PRU_Training:_Hands-on_Labs#LAB_5:_RPMsg_Communication_between_ARM_and_PRU with the pru-software-support package at [2] and the sample rpmsg-client driver. NOTE: you no longer need to build and run PRU_Halt example as shown in the tutorial. cheers, -roger [1] https://lkml.org/lkml/2018/11/22/948 [2] https://github.com/rogerq/pru-software-support-package/commits/upstream/pruss Roger Quadros (2): remoteproc/pru: Add pru_rproc_set_ctable() function remoteproc/pru: Add support for INTC Interrupt map resource Suman Anna (9): remoteproc: Extend rproc_da_to_va() API with a flags parameter remoteproc: Add a rproc_set_firmware() API remoteproc: Add support to handle device specific resource types remoteproc/pru: Add PRU remoteproc driver remoteproc/pru: Add pru-specific debugfs support dt-bindings: remoteproc: ti-pruss: Update bindings for supporting rpmsg remoteproc/pru: Add support for virtio rpmsg stack remoteproc/pru: add pru_rproc_get_id() API to retrieve the PRU id soc: ti: pruss: add helper functions to set GPI mode, MII_RT_event and XFR Tero Kristo (5): remoteproc/pru: add APIs to get and put the PRU cores dt-bindings: remoteproc: ti-pruss: Document application node bindings remoteproc/pru: add support for configuring GPMUX based on client setup remoteproc/pru: configure firmware based on client setup remoteproc/pru: add support for parsing pru interrupt mapping from DT .../devicetree/bindings/soc/ti/ti,pruss.txt | 82 ++ drivers/remoteproc/Kconfig | 16 + drivers/remoteproc/Makefile | 1 + drivers/remoteproc/imx_rproc.c | 2 +- drivers/remoteproc/keystone_remoteproc.c | 3 +- drivers/remoteproc/pru_rproc.c | 1138 ++++++++++++++++++++ drivers/remoteproc/pru_rproc.h | 55 + drivers/remoteproc/qcom_q6v5_mss.c | 5 +- drivers/remoteproc/qcom_q6v5_pas.c | 2 +- drivers/remoteproc/qcom_q6v5_wcss.c | 2 +- drivers/remoteproc/qcom_wcnss.c | 2 +- drivers/remoteproc/remoteproc_core.c | 112 +- drivers/remoteproc/remoteproc_debugfs.c | 3 + drivers/remoteproc/remoteproc_elf_loader.c | 6 +- drivers/remoteproc/remoteproc_internal.h | 2 +- drivers/remoteproc/remoteproc_sysfs.c | 33 +- drivers/remoteproc/st_slim_rproc.c | 3 +- drivers/remoteproc/wkup_m3_rproc.c | 3 +- include/linux/pruss.h | 168 +++ include/linux/remoteproc.h | 32 +- 20 files changed, 1620 insertions(+), 50 deletions(-) create mode 100644 drivers/remoteproc/pru_rproc.c create mode 100644 drivers/remoteproc/pru_rproc.h -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
next reply other threads:[~2018-11-26 7:52 UTC|newest] Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-11-26 7:52 Roger Quadros [this message] 2018-11-26 7:52 ` [PATCH 00/16] remoteproc: Add support for TI PRU Roger Quadros 2018-11-26 7:52 ` [PATCH 01/16] remoteproc: Extend rproc_da_to_va() API with a flags parameter Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 21:29 ` David Lechner 2018-11-29 10:29 ` Roger Quadros 2018-11-29 10:29 ` Roger Quadros 2018-11-29 16:12 ` David Lechner 2018-12-04 10:03 ` Roger Quadros 2018-12-04 10:03 ` Roger Quadros 2019-02-14 3:35 ` Suman Anna 2019-02-14 3:35 ` Suman Anna 2018-11-26 7:52 ` [PATCH 02/16] remoteproc: Add a rproc_set_firmware() API Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 21:41 ` David Lechner 2018-11-29 8:51 ` Roger Quadros 2018-11-29 8:51 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 03/16] remoteproc: Add support to handle device specific resource types Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 04/16] remoteproc/pru: Add PRU remoteproc driver Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 22:32 ` David Lechner 2018-11-29 9:26 ` Roger Quadros 2018-11-29 9:26 ` Roger Quadros 2018-11-30 21:39 ` Dimitar Dimitrov 2018-12-04 8:47 ` Roger Quadros 2018-12-04 8:47 ` Roger Quadros 2018-12-14 9:53 ` Roger Quadros 2018-12-14 9:53 ` Roger Quadros 2018-12-15 13:43 ` Dimitar Dimitrov 2018-11-26 7:52 ` [PATCH 05/16] remoteproc/pru: Add pru-specific debugfs support Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 22:37 ` David Lechner 2018-11-29 10:17 ` Roger Quadros 2018-11-29 10:17 ` Roger Quadros 2018-12-18 15:51 ` Roger Quadros 2018-12-18 15:51 ` Roger Quadros 2018-12-19 12:38 ` Mark Brown 2018-12-19 15:43 ` Roger Quadros 2018-12-19 15:43 ` Roger Quadros 2018-12-19 15:48 ` David Lechner 2018-12-19 17:07 ` Mark Brown 2018-12-19 17:18 ` Tony Lindgren 2018-12-20 8:45 ` Roger Quadros 2018-12-20 8:45 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 06/16] dt-bindings: remoteproc: ti-pruss: Update bindings for supporting rpmsg Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 07/16] remoteproc/pru: Add support for virtio rpmsg stack Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 08/16] remoteproc/pru: Add pru_rproc_set_ctable() function Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 09/16] remoteproc/pru: add APIs to get and put the PRU cores Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 10/16] remoteproc/pru: add pru_rproc_get_id() API to retrieve the PRU id Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 11/16] soc: ti: pruss: add helper functions to set GPI mode, MII_RT_event and XFR Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 12/16] dt-bindings: remoteproc: ti-pruss: Document application node bindings Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 23:27 ` David Lechner 2018-11-29 10:07 ` Roger Quadros 2018-11-29 10:07 ` Roger Quadros 2018-11-29 16:33 ` David Lechner 2018-11-30 11:42 ` Roger Quadros 2018-11-30 11:42 ` Roger Quadros 2018-12-11 22:06 ` Rob Herring 2018-12-17 16:03 ` Roger Quadros 2018-12-17 16:03 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 13/16] remoteproc/pru: add support for configuring GPMUX based on client setup Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 14/16] remoteproc/pru: configure firmware " Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 15/16] remoteproc/pru: add support for parsing pru interrupt mapping from DT Roger Quadros 2018-11-26 7:52 ` Roger Quadros 2018-11-26 7:52 ` [PATCH 16/16] remoteproc/pru: Add support for INTC Interrupt map resource Roger Quadros 2018-11-26 7:52 ` Roger Quadros
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=1543218769-5507-1-git-send-email-rogerq@ti.com \ --to=rogerq@ti.com \ --cc=bcousson@baylibre.com \ --cc=bjorn.andersson@linaro.org \ --cc=devicetree@vger.kernel.org \ --cc=jreeder@ti.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=linux-remoteproc@vger.kernel.org \ --cc=m-karicheri2@ti.com \ --cc=nsaulnier@ti.com \ --cc=nsekhar@ti.com \ --cc=ohad@wizery.com \ --cc=robh+dt@kernel.org \ --cc=s-anna@ti.com \ --cc=ssantosh@kernel.org \ --cc=t-kristo@ti.com \ --cc=tony@atomide.com \ --cc=woods.technical@gmail.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.