From: Komal Bajaj <quic_kbajaj@quicinc.com>
To: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Melody Olvera <quic_molvera@quicinc.com>,
Komal Bajaj <quic_kbajaj@quicinc.com>
Subject: [PATCH v3 0/4]remoteproc: qcom_q6v5_pas: Add support for QDU1000/QRU1000 mpss
Date: Thu, 20 Jun 2024 17:31:39 +0530 [thread overview]
Message-ID: <20240620120143.12375-1-quic_kbajaj@quicinc.com> (raw)
This patchset adds support for the mpss found in the QDU1000 and QRU1000
SoCs.
The mpss boot process now supports late attach for an already running
mpss. For this, it uses an RMB register space to perform a handshake
with the mpss for the late attach process. This is implemented in the
patches below. The patches also address issues with split binary
detection to support loading of split binaries more robustly.
Changes from v2:
* Collected Acked-by tag
* Listed the items in reg property in qdu1000-mpss-pas bindings
* Marked memory-region as required property
* Moved rmb register logic to pas driver
* Moved the logic to signal Q6 to continute booting into a helper
function
* Link to v2: https://lore.kernel.org/linux-arm-msm/20230306231202.12223-1-quic_molvera@quicinc.com/
Changes from v1:
* Dropped changes to aoss-qmp
* Renamed mpss pas bindings
* Updated commit msg on mdt loader to be more descriptive
* Fixed syntax errors in bindings
* Updated firmware name in bindings
Komal Bajaj (1):
remoteproc: qcom_q6v5_pas: Add QDU1000/QRU1000 mpss compatible
Melody Olvera (3):
dt-bindings: remoteproc: mpss: Document QDU1000/QRU1000 mpss devices
remoteproc: qcom: q6v5: Add support for q6 rmb registers
remoteproc: qcom_q6v5_pas: Add support to attach a DSP
.../remoteproc/qcom,qdu1000-mpss-pas.yaml | 129 ++++++++++++++++++
drivers/remoteproc/qcom_q6v5.h | 8 ++
drivers/remoteproc/qcom_q6v5_pas.c | 107 +++++++++++++++
3 files changed, 244 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/qcom,qdu1000-mpss-pas.yaml
--
2.42.0
next reply other threads:[~2024-06-20 12:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 12:01 Komal Bajaj [this message]
2024-06-20 12:01 ` [PATCH v3 1/4] dt-bindings: remoteproc: mpss: Document QDU1000/QRU1000 mpss devices Komal Bajaj
2024-06-20 13:20 ` Krzysztof Kozlowski
2024-06-20 13:45 ` Rob Herring (Arm)
2024-06-20 12:01 ` [PATCH v3 2/4] remoteproc: qcom: q6v5: Add support for q6 rmb registers Komal Bajaj
2024-06-20 21:38 ` Dmitry Baryshkov
2024-06-20 12:01 ` [PATCH v3 3/4] remoteproc: qcom_q6v5_pas: Add support to attach a DSP Komal Bajaj
2024-06-20 21:58 ` Dmitry Baryshkov
2024-06-25 20:03 ` Bjorn Andersson
2024-06-20 12:01 ` [PATCH v3 4/4] remoteproc: qcom_q6v5_pas: Add QDU1000/QRU1000 mpss compatible Komal Bajaj
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=20240620120143.12375-1-quic_kbajaj@quicinc.com \
--to=quic_kbajaj@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_molvera@quicinc.com \
--cc=robh@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 read-only IMAP folder(s) and NNTP newsgroup(s).