From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Cc: ohad@wizery.com, bjorn.andersson@linaro.org, s-anna@ti.com,
linux-remoteproc@vger.kernel.org, robh+dt@kernel.org,
lee.jones@linaro.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, praneeth@ti.com,
rogerq@ti.com
Subject: Re: [PATCH v2 6/6] remoteproc/pru: Add support for various PRU cores on K3 J721E SoCs
Date: Thu, 3 Dec 2020 11:53:32 -0700 [thread overview]
Message-ID: <20201203185332.GC1392978@xps15> (raw)
In-Reply-To: <20201119140850.12268-7-grzegorz.jaszczyk@linaro.org>
On Thu, Nov 19, 2020 at 03:08:50PM +0100, Grzegorz Jaszczyk wrote:
> From: Suman Anna <s-anna@ti.com>
>
> The K3 J721E family of SoCs have a revised version of the AM65x ICSSG IP
> and contains two instances of this newer ICSSG IP. Each ICSSG processor
> subsystem contains 2 primary PRU cores, 2 auxiliary PRU cores called RTUs,
> and 2 new auxiliary cores called Transmit PRUs (Tx_PRUs).
>
> Enhance the existing PRU remoteproc driver to support these new PRU
> and RTU cores by using specific compatibles. The cores have the same
> memory copying limitations as on AM65x, so reuses the custom memcpy
> function within the driver's ELF loader implementation. The initial
> names for the firmware images for each PRU core are retrieved from
> DT nodes, and can be adjusted through sysfs if required.
>
> Signed-off-by: Suman Anna <s-anna@ti.com>
> Co-developed-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
> Signed-off-by: Grzegorz Jaszczyk <grzegorz.jaszczyk@linaro.org>
Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> ---
> drivers/remoteproc/pru_rproc.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/remoteproc/pru_rproc.c b/drivers/remoteproc/pru_rproc.c
> index 48c1c51e0d42..96f689283a8b 100644
> --- a/drivers/remoteproc/pru_rproc.c
> +++ b/drivers/remoteproc/pru_rproc.c
> @@ -852,6 +852,9 @@ static const struct of_device_id pru_rproc_match[] = {
> { .compatible = "ti,am654-pru", .data = &k3_pru_data },
> { .compatible = "ti,am654-rtu", .data = &k3_rtu_data },
> { .compatible = "ti,am654-tx-pru", .data = &k3_tx_pru_data },
> + { .compatible = "ti,j721e-pru", .data = &k3_pru_data },
> + { .compatible = "ti,j721e-rtu", .data = &k3_rtu_data },
> + { .compatible = "ti,j721e-tx-pru", .data = &k3_tx_pru_data },
> {},
> };
> MODULE_DEVICE_TABLE(of, pru_rproc_match);
> --
> 2.29.0
>
next prev parent reply other threads:[~2020-12-03 18:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 14:08 [PATCH v2 0/6] Add a PRU remoteproc driver Grzegorz Jaszczyk
2020-11-19 14:08 ` [PATCH v2 1/6] dt-bindings: remoteproc: Add binding doc for PRU cores in the PRU-ICSS Grzegorz Jaszczyk
2020-11-19 14:08 ` [PATCH v2 2/6] remoteproc/pru: Add a PRU remoteproc driver Grzegorz Jaszczyk
2020-12-01 22:54 ` Mathieu Poirier
2020-12-02 20:53 ` Mathieu Poirier
2020-12-02 21:13 ` Mathieu Poirier
2020-12-03 23:42 ` Suman Anna
2020-12-04 14:09 ` Grzegorz Jaszczyk
2020-11-19 14:08 ` [PATCH v2 3/6] remoteproc/pru: Add support for PRU specific interrupt configuration Grzegorz Jaszczyk
2020-12-02 22:57 ` Mathieu Poirier
2020-12-04 14:11 ` Grzegorz Jaszczyk
2020-12-04 17:40 ` Mathieu Poirier
2020-11-19 14:08 ` [PATCH v2 4/6] remoteproc/pru: Add pru-specific debugfs support Grzegorz Jaszczyk
2020-12-03 18:21 ` Mathieu Poirier
2020-12-04 14:12 ` Grzegorz Jaszczyk
2020-11-19 14:08 ` [PATCH v2 5/6] remoteproc/pru: Add support for various PRU cores on K3 AM65x SoCs Grzegorz Jaszczyk
2020-12-03 18:51 ` Mathieu Poirier
2020-12-04 14:13 ` Grzegorz Jaszczyk
2020-11-19 14:08 ` [PATCH v2 6/6] remoteproc/pru: Add support for various PRU cores on K3 J721E SoCs Grzegorz Jaszczyk
2020-12-03 18:53 ` Mathieu Poirier [this message]
2020-12-04 14:14 ` Grzegorz Jaszczyk
2020-12-04 15:05 ` [PATCH v2 0/6] Add a PRU remoteproc driver Suman Anna
2020-12-04 15:11 ` Grzegorz Jaszczyk
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=20201203185332.GC1392978@xps15 \
--to=mathieu.poirier@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grzegorz.jaszczyk@linaro.org \
--cc=lee.jones@linaro.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=ohad@wizery.com \
--cc=praneeth@ti.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=s-anna@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;
as well as URLs for NNTP newsgroup(s).