From: Bjorn Andersson <andersson@kernel.org>
To: Shawn Guo <shengchao.guo@oss.qualcomm.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Manivannan Sadhasivam <mani@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v5 0/3] Add ADSP and CDSP support for Nord SoC
Date: Thu, 30 Jul 2026 22:26:36 -0500 [thread overview]
Message-ID: <178546838835.317434.4276793731151005966.b4-ty@kernel.org> (raw)
In-Reply-To: <20260729023508.879752-1-shengchao.guo@oss.qualcomm.com>
On Wed, 29 Jul 2026 10:35:05 +0800, Shawn Guo wrote:
> The series documents AOSS side channel, adds ADSP (HPASS DSP) and
> 4 CDSPs support for Nord SoC.
>
> Nord SoC actually has 3 ADSPs. This series only enables ADSP0 which
> can work independently. The rest two instances have dependencies on
> ADSP0 regarding start/stop and SSR. And remoteproc framework doesn't
> seem to support such "slave" instances yet.
>
> [...]
Applied, thanks!
[2/3] dt-bindings: remoteproc: qcom,nord-pas: Document Nord PAS
commit: f0b6c2b40f78db917e72a5d273b031e99ab2c0e7
[3/3] remoteproc: qcom: pas: Add Nord ADSP and CDSP support
commit: 29a24fe87bc80d81fc5d3b0d7e7615985c0ac29d
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-07-31 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 2:35 Shawn Guo
2026-07-29 2:35 ` [PATCH v5 1/3] dt-bindings: soc: qcom,aoss-qmp: Document Nord AOSS side channel Shawn Guo
2026-07-29 2:35 ` [PATCH v5 2/3] dt-bindings: remoteproc: qcom,nord-pas: Document Nord PAS Shawn Guo
2026-07-29 2:35 ` [PATCH v5 3/3] remoteproc: qcom: pas: Add Nord ADSP and CDSP support Shawn Guo
2026-07-31 3:26 ` Bjorn Andersson [this message]
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=178546838835.317434.4276793731151005966.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@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=mani@kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
--cc=shengchao.guo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®