From: Sumit Garg <sumit.garg@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Vignesh Viswanathan <vignesh.viswanathan@oss.qualcomm.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Add support for IPQ9650 CDSP remoteproc
Date: Tue, 9 Jun 2026 10:40:26 +0530 [thread overview]
Message-ID: <aiegQubVKWXs3MXw@sumit-xelite> (raw)
In-Reply-To: <aieAnN35K_WarmUD@baldur>
Hi Bjorn,
On Mon, Jun 08, 2026 at 09:59:35PM -0500, Bjorn Andersson wrote:
> On Wed, May 20, 2026 at 12:56:16AM +0530, Vignesh Viswanathan wrote:
> > Add changes to enable IPQ9650 CDSP. This series adds new Devicetree
> > bindings for IPQ9650 PAS and also adds required changes in qcom_q6v5_pas
> > driver to support IPQ9650 CDSP remoteproc.
> >
> > This series depends on [1], [2] and [3] to functionally bring up the CDSP
> > remoteproc on IPQ9650, but does not contain any compilation dependencies.
> >
> > [1] https://lore.kernel.org/linux-arm-msm/20260518072856.22790-1-sumit.garg@kernel.org/
>
> I'm not able to determine why this is a dependency from cover letter,
> commit messages, or the patches. If you have a dependency on this series
> this isn't your typical PAS-based subsystem, so describing what it is in
> the cover letter would be wonderful.
Probably the cover letter didn't mention that this IPQ chipset runs
OP-TEE/TF-A as the TZ, that's why it's unclear. Without the OP-TEE PAS
series, the CDSP can't be brought up on this chipset. Similar would be
the case for all other Qcom chipsets supporting OP-TEE.
Not sure if there is anything missing for the OP-TEE PAS series to be
picked up. Surely we missed the current merge window but hopeful you
will be able to give some attention to that series for the next merge
window.
-Sumit
>
> > [2] https://lore.kernel.org/linux-arm-msm/20260519-mp8899-regulator-driver-v1-0-30d14421b7f1@oss.qualcomm.com/T/#t
> > [3] https://lore.kernel.org/linux-arm-msm/20260520-cdsp-power-v1-0-85eb9501a1cd@oss.qualcomm.com/T/#t
>
> #3 is a fundamental part of the addition of this remoteproc driver and
> the solution would be better reviewed as a whole - so you should send
> the two parts in the same series.
>
> PS. If you run "git log --oneline" you will see that there shouldn't be
> a "drivers:" prefix in your subject.
>
> Regards,
> Bjorn
>
> >
> > ---
> > Vignesh Viswanathan (2):
> > dt-bindings: remoteproc: Document IPQ9650 Compute DSP
> > drivers: remoteproc: qcom_q6v5_pas: Add support for IPQ9650 CDSP
> >
> > .../bindings/remoteproc/qcom,ipq9650-pas.yaml | 136 +++++++++++++++++++++
> > drivers/remoteproc/qcom_q6v5_pas.c | 38 +++++-
> > 2 files changed, 172 insertions(+), 2 deletions(-)
> > ---
> > base-commit: 6a50ba100ace43f43c87384367eb2d2605fcc16c
> > change-id: 20260520-ipq9650-remoteproc-9aa8c6d05de3
> >
> > Best regards,
> > --
> > Vignesh Viswanathan <vignesh.viswanathan@oss.qualcomm.com>
> >
next prev parent reply other threads:[~2026-06-09 5:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 19:26 [PATCH 0/2] Add support for IPQ9650 CDSP remoteproc Vignesh Viswanathan
2026-05-19 19:26 ` [PATCH 1/2] dt-bindings: remoteproc: Document IPQ9650 Compute DSP Vignesh Viswanathan
2026-05-19 23:11 ` Rob Herring (Arm)
2026-05-20 10:06 ` Konrad Dybcio
2026-05-26 7:39 ` Vignesh Viswanathan
2026-05-20 10:52 ` Krzysztof Kozlowski
2026-05-19 19:26 ` [PATCH 2/2] drivers: remoteproc: qcom_q6v5_pas: Add support for IPQ9650 CDSP Vignesh Viswanathan
2026-06-09 2:59 ` [PATCH 0/2] Add support for IPQ9650 CDSP remoteproc Bjorn Andersson
2026-06-09 5:10 ` Sumit Garg [this message]
2026-06-09 5:31 ` Vignesh Viswanathan
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=aiegQubVKWXs3MXw@sumit-xelite \
--to=sumit.garg@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--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=robh@kernel.org \
--cc=vignesh.viswanathan@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.