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 v2 0/4] TI K3 R5F remoteproc support
Date: Mon, 29 Jun 2020 21:49:18 -0500 [thread overview]
Message-ID: <20200630024922.32491-1-s-anna@ti.com> (raw)
Hi All,
The following is v2 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.
The patches are based off 5.8-rc1 and now sit on top of the v3 K3 DSP C66x
and C71x remoteproc driver series [2][3] (v1 had R5F followed by DSPs).
The v2 version now only has 4 patches instead of the 7 patches in v1. The
first 2 patches from v1 are already part of 5.8-rc1 and the third patch is
moved to the K3 DSP C66x series [4].
The following is the summary of the main changes in v2:
- Reworked bindings patch (patch #1) to leverage a new common ti-sci-proc
yaml bindings file introduced in the K3 DSP C66x series.
- K3 R5F remoteproc driver revised to leverage more devm_ API and
address all Mathieu's comments.
Please see the individual patches for detailed delta differences.
regards
Suman
[1] R5F v1: https://patchwork.kernel.org/cover/11456367/
[2] C66x v3: https://patchwork.kernel.org/cover/11602331/
[3] C71x v3: https://patchwork.kernel.org/cover/11602345/
[4] https://patchwork.kernel.org/patch/11602329/
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 | 278 ++++
drivers/remoteproc/Kconfig | 13 +
drivers/remoteproc/Makefile | 1 +
drivers/remoteproc/ti_k3_r5_remoteproc.c | 1396 +++++++++++++++++
4 files changed, 1688 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-06-30 2:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 2:49 Suman Anna [this message]
2020-06-30 2:49 ` [PATCH v2 1/4] dt-bindings: remoteproc: Add bindings for R5F subsystem on TI K3 SoCs Suman Anna
2020-07-14 17:15 ` Rob Herring
2020-07-16 17:19 ` Mathieu Poirier
2020-07-16 19:43 ` Stefano Stabellini
2020-07-27 22:39 ` Suman Anna
2020-08-10 16:52 ` Suman Anna
2020-08-20 21:53 ` Suman Anna
2020-08-24 20:42 ` Ben Levinsky
2020-06-30 2:49 ` [PATCH v2 2/4] remoteproc: k3-r5: Add a remoteproc driver for R5F subsystem Suman Anna
2020-07-09 18:10 ` Mathieu Poirier
2020-07-09 22:02 ` Suman Anna
2020-06-30 2:49 ` [PATCH v2 3/4] remoteproc: k3-r5: Initialize TCM memories for ECC Suman Anna
2020-07-09 19:29 ` Mathieu Poirier
2020-06-30 2:49 ` [PATCH v2 4/4] remoteproc: k3-r5: Add loading support for on-chip SRAM regions Suman Anna
2020-07-09 19:51 ` Mathieu Poirier
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=20200630024922.32491-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).