From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.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 v4 0/4] TI K3 R5F remoteproc support
Date: Tue, 8 Sep 2020 12:45:52 -0500 [thread overview]
Message-ID: <20200908174556.21277-1-s-anna@ti.com> (raw)
Hi All,
The following is v4 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 a rebased version on top of the latest v5.9-rc baseline and
includes very minor fixes w.r.t v3. The previous K3 DSP dependencies are now
available in mainline kernel. Please see the individual patches for the delta
differences (Only patches 1 and 2 updated).
Bjorn,
This series is only waiting on bindings ack and the conclusion on the bindings
discussion from v2 [4] on which I haven't seen any forward progress on this
despite all the clarifications. I do not expect any changes even w.r.t System DT,
and we can't really have a common binding between TI and Xilinx R5Fs. How can we
take this series forward? It is blocking us to get the various usecases that
leverage the remoteprocs upstream.
regards
Suman
[1] R5F v1: https://patchwork.kernel.org/cover/11456367/
[2] R5F v2: https://patchwork.kernel.org/cover/11632993/
[3] R5F v3: https://patchwork.kernel.org/cover/11679327/
[4] https://patchwork.kernel.org/patch/11632997/
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.28.0
next reply other threads:[~2020-09-08 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 17:45 Suman Anna [this message]
2020-09-08 17:45 ` [PATCH v4 1/4] dt-bindings: remoteproc: Add bindings for R5F subsystem on TI K3 SoCs Suman Anna
2020-09-08 17:45 ` [PATCH v4 2/4] remoteproc: k3-r5: Add a remoteproc driver for R5F subsystem Suman Anna
2020-09-08 17:45 ` [PATCH v4 3/4] remoteproc: k3-r5: Initialize TCM memories for ECC Suman Anna
2020-09-08 17:45 ` [PATCH v4 4/4] remoteproc: k3-r5: Add loading support for on-chip SRAM regions Suman Anna
2020-09-22 19:47 ` [PATCH v4 0/4] TI K3 R5F remoteproc support Rob Herring
2020-09-22 20:26 ` 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=20200908174556.21277-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