MIME-Version: 1.0
References: <20201211184811.6490-1-grzegorz.jaszczyk@linaro.org>
In-Reply-To: <20201211184811.6490-1-grzegorz.jaszczyk@linaro.org>
From:   Christian Gmeiner <christian.gmeiner@gmail.com>
Date:   Sun, 26 Dec 2021 14:06:24 +0100
Message-ID: <CAH9NwWcDj1odYuAvMVRG5zMOA-Q95EvoTDqq1o-M-s45NTcwkw@mail.gmail.com>
Subject: Re: [PATCH 0/6] Introduce PRU platform consumer API
To:     Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Cc:     ssantosh@kernel.org, Suman Anna <s-anna@ti.com>,
        santosh.shilimkar@oracle.com, Lee Jones <lee.jones@linaro.org>,
        LKML <linux-kernel@vger.kernel.org>, linux-omap@vger.kernel.org,
        linux-arm-kernel@lists.infradead.org, praneeth@ti.com,
        Tony Lindgren <tony@atomide.com>,
        linux-remoteproc@vger.kernel.org,
        Mathieu Poirier <mathieu.poirier@linaro.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

HI all.

Am Fr., 11. Dez. 2020 um 20:15 Uhr schrieb Grzegorz Jaszczyk
<grzegorz.jaszczyk@linaro.org>:
>
> 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. Two first 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
>
> The third one [1] was accepted and applied to andersson/remoteproc.git
> (refs/heads/for-next): [2] but is not merged yet.
>
> 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 patch set depends on "Introduce PRU remoteproc consumer API" set [3], which
> is complementary to this one but goes for different, remoteproc sub-system.
>
> [1] https://patchwork.kernel.org/project/linux-arm-kernel/cover/20201208141002.17777-1-grzegorz.jaszczyk@linaro.org/
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/andersson/remoteproc.git/commit/?h=for-next&id=b44786c9bdc46eac8388843f0a6116369cb18bca
> [3] https://patchwork.kernel.org/project/linux-arm-kernel/cover/20201211142933.25784-1-grzegorz.jaszczyk@linaro.org/
>
> Best regards,
> Grzegorz
>
> Andrew F. Davis (1):
>   soc: ti: pruss: Add pruss_{request,release}_mem_region() API
>
> Suman Anna (3):
>   soc: ti: pruss: Add pruss_cfg_read()/update() API
>   soc: ti: pruss: Add helper functions to set GPI mode, MII_RT_event and
>     XFR
>   soc: ti: pruss: Add helper function to enable OCP master ports
>
> 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       | 257 ++++++++++++++++++++++++++++++++++-
>  include/linux/pruss.h        | 221 ++++++++++++++++++++++++++++++
>  include/linux/pruss_driver.h |  72 +++++++---
>  3 files changed, 526 insertions(+), 24 deletions(-)
>
> --
> 2.29.0
>

Is there any update on this patch series?

-- 
greets
--
Christian Gmeiner, MSc

https://christian-gmeiner.info/privacypolicy