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 0/3] TI K3 DSP remoteproc driver for C66x DSPs
Date: Wed, 25 Mar 2020 15:18:36 -0500 [thread overview]
Message-ID: <20200325201839.15896-1-s-anna@ti.com> (raw)
Hi All,
The following series adds a new K3 DSP remoteproc driver supporting the
C66x DSPs on the TI K3 J721E SoCs. The current series mainly adds the support
for booting the DSPs from the Linux kernel. This series forms the foundation
for adding support for a new 64-bit DSP (C71x DSP) to be posted in a separate
series. Support for attaching to pre-booted DSPs (from bootloader) will be
done in a future series.
The C66x DSPs can boot either using firmware segments loaded into either DDR
and/or internal DSP RAMs. IPC is through the virtio-rpmsg transport. There is
no Error Recovery or Power Management support at present. The driver also does
not support loading into on-chip SRAMs at present.
The patches are based on the current rproc-next branch, and does use couple
of patches posted earlier from the OMAP remoteproc series [1] and TI K3 R5F
series [2]. It also leverages the fixed memory carveout fixes series [3].
Following is the patch summary:
- Patch 1 adds the bindings in the YAML format.
- Patch 2 adds the basic remoteproc driver for the C66x DSPs
- Patch 3 is an enhancement to support loading into the DSP's internal
RAMs directly.
regards
Suman
[1] https://patchwork.kernel.org/patch/11455135/
[2] https://patchwork.kernel.org/patch/11456383/
[3] https://patchwork.kernel.org/cover/11447649/
Suman Anna (3):
dt-bindings: remoteproc: Add bindings for C66x DSPs on TI K3 SoCs
remoteproc/k3-dsp: Add a remoteproc driver of K3 C66x DSPs
remoteproc/k3-dsp: Add support for L2RAM loading on C66x DSPs
.../bindings/remoteproc/ti,k3-dsp-rproc.yaml | 180 ++++
drivers/remoteproc/Kconfig | 16 +
drivers/remoteproc/Makefile | 1 +
drivers/remoteproc/ti_k3_dsp_remoteproc.c | 818 ++++++++++++++++++
4 files changed, 1015 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-dsp-rproc.yaml
create mode 100644 drivers/remoteproc/ti_k3_dsp_remoteproc.c
--
2.23.0
next reply other threads:[~2020-03-25 20:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 20:18 Suman Anna [this message]
2020-03-25 20:18 ` [PATCH 1/3] dt-bindings: remoteproc: Add bindings for C66x DSPs on TI K3 SoCs Suman Anna
2020-03-26 16:54 ` Rob Herring
2020-04-27 19:49 ` Mathieu Poirier
2020-05-13 17:20 ` Suman Anna
2020-03-25 20:18 ` [PATCH 2/3] remoteproc/k3-dsp: Add a remoteproc driver of K3 C66x DSPs Suman Anna
2020-04-27 22:57 ` Mathieu Poirier
2020-05-13 18:14 ` Suman Anna
2020-05-13 19:40 ` Mathieu Poirier
2020-03-25 20:18 ` [PATCH 3/3] remoteproc/k3-dsp: Add support for L2RAM loading on " Suman Anna
2020-04-28 19:58 ` Mathieu Poirier
2020-04-28 20:09 ` Mathieu Poirier
2020-05-13 22:31 ` 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=20200325201839.15896-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).