From: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
To: robh@kernel.org, srini@kernel.org, amahesh@qti.qualcomm.com,
krzk+dt@kernel.org, conor+dt@kernel.org, andersson@kernel.org,
konradybcio@kernel.org
Cc: mathieu.poirier@linaro.org, linux-arm-msm@vger.kernel.org,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org,
mani@kernel.org
Subject: [PATCH V4 1/5] dt-bindings: remoteproc: qcom, sm8550-pas: Add Glymur ADSP
Date: Tue, 10 Mar 2026 09:06:13 +0530 [thread overview]
Message-ID: <20260310033617.3108675-2-sibi.sankar@oss.qualcomm.com> (raw)
In-Reply-To: <20260310033617.3108675-1-sibi.sankar@oss.qualcomm.com>
Document compatible for Qualcomm Glymur ADSP PAS which is fully
compatible with Qualcomm Kaanapali ADSP PAS.
Signed-off-by: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
---
.../devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml
index b117c82b057b..fb6e0b4f54e8 100644
--- a/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml
+++ b/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml
@@ -29,6 +29,7 @@ properties:
- qcom,x1e80100-cdsp-pas
- items:
- enum:
+ - qcom,glymur-adsp-pas
- qcom,kaanapali-adsp-pas
- qcom,sm8750-adsp-pas
- const: qcom,sm8550-adsp-pas
@@ -101,6 +102,7 @@ allOf:
compatible:
contains:
enum:
+ - qcom,glymur-adsp-pas
- qcom,kaanapali-adsp-pas
- qcom,kaanapali-cdsp-pas
- qcom,sm8750-adsp-pas
--
2.34.1
next prev parent reply other threads:[~2026-03-10 3:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 3:36 [PATCH V4 0/5] Enable ADSP and CDSP for Glymur SoC Sibi Sankar
2026-03-10 3:36 ` Sibi Sankar [this message]
2026-03-10 7:50 ` [PATCH V4 1/5] dt-bindings: remoteproc: qcom,sm8550-pas: Add Glymur ADSP Krzysztof Kozlowski
2026-03-10 9:17 ` Sibi Sankar
2026-03-11 3:43 ` Claude review: dt-bindings: remoteproc: qcom, sm8550-pas: " Claude Code Review Bot
2026-03-10 3:36 ` [PATCH V4 2/5] dt-bindings: remoteproc: qcom, sm8550-pas: Add Glymur CDSP Sibi Sankar
2026-03-11 3:43 ` Claude review: " Claude Code Review Bot
2026-03-10 3:36 ` [PATCH V4 3/5] dt-bindings: misc: qcom, fastrpc: Add compatible for Glymur Sibi Sankar
2026-03-10 7:52 ` [PATCH V4 3/5] dt-bindings: misc: qcom,fastrpc: " Krzysztof Kozlowski
2026-03-11 3:43 ` Claude review: dt-bindings: misc: qcom, fastrpc: " Claude Code Review Bot
2026-03-10 3:36 ` [PATCH V4 4/5] arm64: dts: qcom: glymur: Add ADSP and CDSP for Glymur SoC Sibi Sankar
2026-03-11 3:43 ` Claude review: " Claude Code Review Bot
2026-03-10 3:36 ` [PATCH V4 5/5] arm64: dts: qcom: glymur-crd: Enable ADSP and CDSP Sibi Sankar
2026-03-11 3:43 ` Claude review: " Claude Code Review Bot
2026-03-11 3:43 ` Claude review: Enable ADSP and CDSP for Glymur SoC Claude Code Review Bot
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=20260310033617.3108675-2-sibi.sankar@oss.qualcomm.com \
--to=sibi.sankar@oss.qualcomm.com \
--cc=amahesh@qti.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.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=srini@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