From: Suman Anna <s-anna@ti.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Hari Nagalla <hnagalla@ti.com>,
Praneeth Bajjuri <praneeth@ti.com>,
<linux-remoteproc@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, Suman Anna <s-anna@ti.com>
Subject: [PATCH v3 0/5] K3 R5F & DSP IPC-only mode support
Date: Sun, 13 Feb 2022 14:12:41 -0600 [thread overview]
Message-ID: <20220213201246.25952-1-s-anna@ti.com> (raw)
Hi All,
The following is a revised version (v3) of the series that adds the
IPC-only mode support for the TI K3 R5F and DSP (C66x and C71x) remoteprocs
covering AM65x, J721E, J7200, AM64x and the recently added J721S2 SoCs.
Patches are on top of 5.17-rc2 (since rproc-next is baselined on rc2).
Please see the v1 cover-letter [1] for the design details of the
'IPC-only' mode functionality.
The following are the main changes w.r.t v2 [2], please see the individual
patches for the exact deltas:
- The first patch in v2 "remoteproc: Add support for detach-only during
shutdown" is dropped
- Added a new "remoteproc: Change rproc_shutdown() to return a status"
patch as the first patch in v3.
- Adjusted the K3 R5F and DSP remoteproc drivers to invoke
rproc_detach() in the case of IPC-only mode during teardown
The following is a summary of patches in v3:
- Patch 1 enhances the remoteproc core to return a status for
rproc_shutdown() that is in turn returned in the sysfs and cdev
interfaces. This replaces the flag-based logic in v2 and is used to
return an error for K3 SoCs that don't supply a .stop() ops in
IPC-only mode.
- Patches 2 and 4 refactor the mailbox request code out of start
in the K3 R5F and DSP remoteproc drivers for reuse in the new attach
callbacks.
- Patch 3 adds the IPC-only mode support for R5F.
- Patch 5 adds the IPC-only mode support for both K3 C66x and C71x
DSPs.
I have re-verified the different combinations on J721E, J7200 and AM65x
SoCs. AM64x currently lacks early-boot support, but the logic is ready
for Single-CPU and Split modes that are specific to AM64x SoCs. J721S2
doesn't have either early-boot support yet, and the dts nodes are also
not added yet, but I have tested locally using additional patches.
regards
Suman
[1] https://patchwork.kernel.org/project/linux-remoteproc/cover/20210522000309.26134-1-s-anna@ti.com/
[2] https://patchwork.kernel.org/project/linux-remoteproc/cover/20210723220248.6554-1-s-anna@ti.com/
Suman Anna (5):
remoteproc: Change rproc_shutdown() to return a status
remoteproc: k3-r5: Refactor mbox request code in start
remoteproc: k3-r5: Add support for IPC-only mode for all R5Fs
remoteproc: k3-dsp: Refactor mbox request code in start
remoteproc: k3-dsp: Add support for IPC-only mode for all K3 DSPs
Documentation/staging/remoteproc.rst | 3 +-
drivers/remoteproc/remoteproc_cdev.c | 2 +-
drivers/remoteproc/remoteproc_core.c | 9 +-
drivers/remoteproc/remoteproc_sysfs.c | 2 +-
drivers/remoteproc/ti_k3_dsp_remoteproc.c | 208 ++++++++++++----
drivers/remoteproc/ti_k3_r5_remoteproc.c | 287 +++++++++++++++++++---
include/linux/remoteproc.h | 2 +-
7 files changed, 431 insertions(+), 82 deletions(-)
--
2.32.0
next reply other threads:[~2022-02-13 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 20:12 Suman Anna [this message]
2022-02-13 20:12 ` [PATCH v3 1/5] remoteproc: Change rproc_shutdown() to return a status Suman Anna
2022-02-13 20:12 ` [PATCH v3 2/5] remoteproc: k3-r5: Refactor mbox request code in start Suman Anna
2022-02-13 20:12 ` [PATCH v3 3/5] remoteproc: k3-r5: Add support for IPC-only mode for all R5Fs Suman Anna
2023-11-02 10:07 ` Jan Kiszka
2023-11-02 15:43 ` Mathieu Poirier
2023-11-02 16:43 ` Jan Kiszka
2023-12-08 11:21 ` Hari Nagalla
2022-02-13 20:12 ` [PATCH v3 4/5] remoteproc: k3-dsp: Refactor mbox request code in start Suman Anna
2022-02-13 20:12 ` [PATCH v3 5/5] remoteproc: k3-dsp: Add support for IPC-only mode for all K3 DSPs 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=20220213201246.25952-1-s-anna@ti.com \
--to=s-anna@ti.com \
--cc=bjorn.andersson@linaro.org \
--cc=hnagalla@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=praneeth@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