From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: Lokesh Vutla <lokeshvutla@ti.com>,
<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Suman Anna <s-anna@ti.com>
Subject: [PATCH v3 0/4] TI K3 R5F remoteproc support
Date: Wed, 22 Jul 2020 18:55:50 -0500 [thread overview]
Message-ID: <20200722235554.7511-1-s-anna@ti.com> (raw)
Hi All,
The following is v3 of the TI K3 R5F remoteproc driver series supporting all
the R5F processor clusters/subsystems on TI AM65x and J721E SoCs. Please
see the v1 cover-letter [1] for the features supported on these R5F processors.
This series is almost ready and awaiting the conclusion on the bindings
discussion from v2.
The patches are rebased and slightly revised versions of v2 to sit on top of
the v5 K3 DSP C66x [2] and v3 C71x remoteproc driver series [3].
Following are the main differences from v2:
- The bindings patch (patch #1) is revised to move away from using the
ti-sci-proc yaml bindings file to the generic refactored ti,k3-sci-common.yaml
bindings patch introduced in the latest K3 DSP C66x series.
- Minor updates to the R5F remoteproc driver (patch #2) fixing all the
pending review comments from Mathieu
Please see the individual patches for detailed delta differences.
regards
Suman
[1] R5F v1: https://patchwork.kernel.org/cover/11456367/
[2] R5F v2: https://patchwork.kernel.org/cover/11632993/
[3] C66x v5: https://patchwork.kernel.org/cover/11676819/
[4] C71x v3: https://patchwork.kernel.org/cover/11602345/
Suman Anna (4):
dt-bindings: remoteproc: Add bindings for R5F subsystem on TI K3 SoCs
remoteproc: k3-r5: Add a remoteproc driver for R5F subsystem
remoteproc: k3-r5: Initialize TCM memories for ECC
remoteproc: k3-r5: Add loading support for on-chip SRAM regions
.../bindings/remoteproc/ti,k3-r5f-rproc.yaml | 281 ++++
drivers/remoteproc/Kconfig | 13 +
drivers/remoteproc/Makefile | 1 +
drivers/remoteproc/ti_k3_r5_remoteproc.c | 1395 +++++++++++++++++
4 files changed, 1690 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-r5f-rproc.yaml
create mode 100644 drivers/remoteproc/ti_k3_r5_remoteproc.c
--
2.26.0
next reply other threads:[~2020-07-22 23:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 23:55 Suman Anna [this message]
2020-07-22 23:55 ` [PATCH v3 1/4] dt-bindings: remoteproc: Add bindings for R5F subsystem on TI K3 SoCs Suman Anna
2020-08-20 21:23 ` Suman Anna
2020-07-22 23:55 ` [PATCH v3 2/4] remoteproc: k3-r5: Add a remoteproc driver for R5F subsystem Suman Anna
2020-07-22 23:55 ` [PATCH v3 3/4] remoteproc: k3-r5: Initialize TCM memories for ECC Suman Anna
2020-07-22 23:55 ` [PATCH v3 4/4] remoteproc: k3-r5: Add loading support for on-chip SRAM regions Suman Anna
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=20200722235554.7511-1-s-anna@ti.com \
--to=s-anna@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=mathieu.poirier@linaro.org \
--cc=robh+dt@kernel.org \
/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).