From: MD Danish Anwar <danishanwar@ti.com> To: "Andrew F. Davis" <afd@ti.com>, Suman Anna <s-anna@ti.com>, Roger Quadros <rogerq@kernel.org>, Vignesh Raghavendra <vigneshr@ti.com>, MD Danish Anwar <danishanwar@ti.com>, Mathieu Poirier <mathieu.poirier@linaro.org>, Bjorn Andersson <andersson@kernel.org>, Santosh Shilimkar <ssantosh@kernel.org>, Nishanth Menon <nm@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> Subject: [PATCH v4 0/5] Introduce PRU platform consumer API Date: Mon, 13 Mar 2023 16:41:22 +0530 [thread overview] Message-ID: <20230313111127.1229187-1-danishanwar@ti.com> (raw) 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. This is the v4 of the old patch series[1]. This doesn't have any functional changes, the old series has been rebased on linux-next (tag: next-20230306). Changes from v3 [1] to v4: *) Added my SoB tags in all patches as earlier SoB tags were missing in few patches. *) Added Roger's RB tags in 3 patches. *) Addressed Roger's comment in patch 4/5 of this series. Added check for invalid GPI mode in pruss_cfg_gpimode() API. *) Removed patch [4] from this series as that patch is no longer required. *) Made pruss_cfg_read() and pruss_cfg_update() APIs internal to pruss.c by removing EXPORT_SYMBOL_GPL and making them static. Now these APIs are internal to pruss.c and PRUSS CFG space is not exposed. *) Moved APIs pruss_cfg_gpimode(), pruss_cfg_miirt_enable(), pruss_cfg_xfr_enable(), pruss_cfg_get_gpmux(), pruss_cfg_set_gpmux() to pruss.c file as they are using APIs pruss_cfg_read / update. Defined these APIs in pruss.h file as other drivers use these APIs to perform respective operations. Changes from v2 to v3: *) No functional changes, the old series has been rebased on linux-next (tag: next-20230306). This series depends on another series which is already merged in the remoteproc tree[2] and is part of v6.3-rc1. This series and the remoteproc series form the PRUSS consumer API which can be used by consumer drivers to utilize the PRUs. One example of the consumer driver is the PRU-ICSSG ethernet driver [3],which depends on this series and the remoteproc series[2]. [1] https://lore.kernel.org/all/20230306110934.2736465-1-danishanwar@ti.com/ [2] https://lore.kernel.org/all/20230106121046.886863-1-danishanwar@ti.com/#t [3] https://lore.kernel.org/all/20230210114957.2667963-1-danishanwar@ti.com/ [4] https://lore.kernel.org/all/20230306110934.2736465-6-danishanwar@ti.com/ Thanks and Regards, Md Danish Anwar Andrew F. Davis (1): soc: ti: pruss: Add pruss_{request,release}_mem_region() API Suman Anna (2): soc: ti: pruss: Add pruss_cfg_read()/update() API soc: ti: pruss: Add helper functions to set GPI mode, MII_RT_event and XFR Tero Kristo (2): soc: ti: pruss: Add pruss_get()/put() API soc: ti: pruss: Add helper functions to get/set PRUSS_CFG_GPMUX drivers/soc/ti/pruss.c | 278 +++++++++++++++++++++++++++++++ include/linux/pruss_driver.h | 28 +--- include/linux/remoteproc/pruss.h | 179 ++++++++++++++++++++ 3 files changed, 463 insertions(+), 22 deletions(-) -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: MD Danish Anwar <danishanwar@ti.com> To: "Andrew F. Davis" <afd@ti.com>, Suman Anna <s-anna@ti.com>, Roger Quadros <rogerq@kernel.org>, Vignesh Raghavendra <vigneshr@ti.com>, MD Danish Anwar <danishanwar@ti.com>, Mathieu Poirier <mathieu.poirier@linaro.org>, Bjorn Andersson <andersson@kernel.org>, Santosh Shilimkar <ssantosh@kernel.org>, Nishanth Menon <nm@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> Subject: [PATCH v4 0/5] Introduce PRU platform consumer API Date: Mon, 13 Mar 2023 16:41:22 +0530 [thread overview] Message-ID: <20230313111127.1229187-1-danishanwar@ti.com> (raw) 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. This is the v4 of the old patch series[1]. This doesn't have any functional changes, the old series has been rebased on linux-next (tag: next-20230306). Changes from v3 [1] to v4: *) Added my SoB tags in all patches as earlier SoB tags were missing in few patches. *) Added Roger's RB tags in 3 patches. *) Addressed Roger's comment in patch 4/5 of this series. Added check for invalid GPI mode in pruss_cfg_gpimode() API. *) Removed patch [4] from this series as that patch is no longer required. *) Made pruss_cfg_read() and pruss_cfg_update() APIs internal to pruss.c by removing EXPORT_SYMBOL_GPL and making them static. Now these APIs are internal to pruss.c and PRUSS CFG space is not exposed. *) Moved APIs pruss_cfg_gpimode(), pruss_cfg_miirt_enable(), pruss_cfg_xfr_enable(), pruss_cfg_get_gpmux(), pruss_cfg_set_gpmux() to pruss.c file as they are using APIs pruss_cfg_read / update. Defined these APIs in pruss.h file as other drivers use these APIs to perform respective operations. Changes from v2 to v3: *) No functional changes, the old series has been rebased on linux-next (tag: next-20230306). This series depends on another series which is already merged in the remoteproc tree[2] and is part of v6.3-rc1. This series and the remoteproc series form the PRUSS consumer API which can be used by consumer drivers to utilize the PRUs. One example of the consumer driver is the PRU-ICSSG ethernet driver [3],which depends on this series and the remoteproc series[2]. [1] https://lore.kernel.org/all/20230306110934.2736465-1-danishanwar@ti.com/ [2] https://lore.kernel.org/all/20230106121046.886863-1-danishanwar@ti.com/#t [3] https://lore.kernel.org/all/20230210114957.2667963-1-danishanwar@ti.com/ [4] https://lore.kernel.org/all/20230306110934.2736465-6-danishanwar@ti.com/ Thanks and Regards, Md Danish Anwar Andrew F. Davis (1): soc: ti: pruss: Add pruss_{request,release}_mem_region() API Suman Anna (2): soc: ti: pruss: Add pruss_cfg_read()/update() API soc: ti: pruss: Add helper functions to set GPI mode, MII_RT_event and XFR Tero Kristo (2): soc: ti: pruss: Add pruss_get()/put() API soc: ti: pruss: Add helper functions to get/set PRUSS_CFG_GPMUX drivers/soc/ti/pruss.c | 278 +++++++++++++++++++++++++++++++ include/linux/pruss_driver.h | 28 +--- include/linux/remoteproc/pruss.h | 179 ++++++++++++++++++++ 3 files changed, 463 insertions(+), 22 deletions(-) -- 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:[~2023-03-13 11:12 UTC|newest] Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-13 11:11 MD Danish Anwar [this message] 2023-03-13 11:11 ` [PATCH v4 0/5] Introduce PRU platform consumer API MD Danish Anwar 2023-03-13 11:11 ` [PATCH v4 1/5] soc: ti: pruss: Add pruss_get()/put() API MD Danish Anwar 2023-03-13 11:11 ` MD Danish Anwar 2023-03-13 16:19 ` Andrew Davis 2023-03-13 16:19 ` Andrew Davis 2023-03-13 11:11 ` [PATCH v4 2/5] soc: ti: pruss: Add pruss_{request,release}_mem_region() API MD Danish Anwar 2023-03-13 11:11 ` MD Danish Anwar 2023-03-17 8:56 ` Roger Quadros 2023-03-17 8:56 ` Roger Quadros 2023-03-20 5:11 ` [EXTERNAL] " Md Danish Anwar 2023-03-20 5:11 ` Md Danish Anwar 2023-03-20 16:18 ` Andrew Davis 2023-03-20 16:18 ` Andrew Davis 2023-03-21 5:23 ` Md Danish Anwar 2023-03-21 5:23 ` Md Danish Anwar 2023-03-21 9:24 ` Roger Quadros 2023-03-21 9:24 ` Roger Quadros 2023-03-21 9:48 ` [EXTERNAL] " Md Danish Anwar 2023-03-21 9:48 ` Md Danish Anwar 2023-03-21 10:23 ` Roger Quadros 2023-03-21 10:23 ` Roger Quadros 2023-03-21 10:45 ` Md Danish Anwar 2023-03-21 10:45 ` Md Danish Anwar 2023-03-13 11:11 ` [PATCH v4 3/5] soc: ti: pruss: Add pruss_cfg_read()/update() API MD Danish Anwar 2023-03-13 11:11 ` MD Danish Anwar 2023-03-15 12:07 ` Roger Quadros 2023-03-15 12:07 ` Roger Quadros 2023-03-16 11:08 ` [EXTERNAL] " Md Danish Anwar 2023-03-16 11:08 ` Md Danish Anwar 2023-03-16 11:29 ` Md Danish Anwar 2023-03-16 11:29 ` Md Danish Anwar 2023-03-16 11:32 ` Roger Quadros 2023-03-16 11:32 ` Roger Quadros 2023-03-16 11:34 ` [EXTERNAL] " Md Danish Anwar 2023-03-16 11:34 ` Md Danish Anwar 2023-03-13 11:11 ` [PATCH v4 4/5] soc: ti: pruss: Add helper functions to set GPI mode, MII_RT_event and XFR MD Danish Anwar 2023-03-13 11:11 ` MD Danish Anwar 2023-03-15 12:22 ` Roger Quadros 2023-03-15 12:22 ` Roger Quadros 2023-03-16 11:05 ` [EXTERNAL] " Md Danish Anwar 2023-03-16 11:05 ` Md Danish Anwar 2023-03-16 11:36 ` Roger Quadros 2023-03-16 11:36 ` Roger Quadros 2023-03-16 11:44 ` Md Danish Anwar 2023-03-16 11:44 ` Md Danish Anwar 2023-03-16 12:19 ` Roger Quadros 2023-03-16 12:19 ` Roger Quadros 2023-03-16 13:11 ` [EXTERNAL] " Md Danish Anwar 2023-03-16 13:11 ` Md Danish Anwar 2023-03-16 14:04 ` Roger Quadros 2023-03-16 14:04 ` Roger Quadros 2023-03-17 5:02 ` [EXTERNAL] " Md Danish Anwar 2023-03-17 5:02 ` Md Danish Anwar 2023-03-17 8:31 ` Roger Quadros 2023-03-17 8:31 ` Roger Quadros 2023-03-17 8:55 ` [EXTERNAL] " Md Danish Anwar 2023-03-17 8:55 ` Md Danish Anwar 2023-03-13 11:11 ` [PATCH v4 5/5] soc: ti: pruss: Add helper functions to get/set PRUSS_CFG_GPMUX MD Danish Anwar 2023-03-13 11:11 ` 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=20230313111127.1229187-1-danishanwar@ti.com \ --to=danishanwar@ti.com \ --cc=afd@ti.com \ --cc=andersson@kernel.org \ --cc=devicetree@vger.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: 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.