From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Vignesh Viswanathan <vignesh.viswanathan@oss.qualcomm.com>,
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>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
sumit.garg@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: remoteproc: Document IPQ9650 Compute DSP
Date: Wed, 20 May 2026 12:06:03 +0200 [thread overview]
Message-ID: <f214d60d-a0a5-4f5b-bb65-8ea9d0bc858c@oss.qualcomm.com> (raw)
In-Reply-To: <20260520-ipq9650-remoteproc-v1-1-542feb6efb2a@oss.qualcomm.com>
On 5/19/26 9:26 PM, Vignesh Viswanathan wrote:
> Add device tree binding documentation for the Qualcomm IPQ9650 CDSP
> Peripheral Authentication Service (PAS). Unlike existing PAS
> implementations, the IPQ9650 CDSP does not require power domains or an XO
> clock, requiring a separate binding.
Your other patchset made me believe there should be a pair of required
supplies instead
Konrad
next prev parent reply other threads:[~2026-05-20 10:06 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 [this message]
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
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=f214d60d-a0a5-4f5b-bb65-8ea9d0bc858c@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--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=sumit.garg@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome