From: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
To: jassisinghbrar@gmail.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, mani@kernel.org, andersson@kernel.org,
mathieu.poirier@linaro.org, konradybcio@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-remoteproc@vger.kernel.org
Subject: [PATCH 2/5] dt-bindings: mailbox: qcom-ipcc: Document Glymur physical client IDs
Date: Thu, 25 Sep 2025 00:07:23 +0530 [thread overview]
Message-ID: <20250924183726.509202-3-sibi.sankar@oss.qualcomm.com> (raw)
In-Reply-To: <20250924183726.509202-1-sibi.sankar@oss.qualcomm.com>
Document the physical client IDs specific to Glymur SoCs. Physical client
IDs are used on newer Qualcomm platforms including Glymur, since the Inter
Process Communication Controller (IPCC) HW block no longer has the virtual
to physical mapping in place.
Signed-off-by: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
---
https://patchwork.kernel.org/project/linux-arm-msm/patch/20250922-ipcc-header-v1-1-f0b12715e118@oss.qualcomm.com/
^^ patch seems to assume physical IDs are common across SoCs but it doesn't
seem to hold true on Glymur.
include/dt-bindings/mailbox/qcom-ipcc.h | 61 +++++++++++++++++++++++++
1 file changed, 61 insertions(+)
diff --git a/include/dt-bindings/mailbox/qcom-ipcc.h b/include/dt-bindings/mailbox/qcom-ipcc.h
index fd85a79381b3..61cef29e43f0 100644
--- a/include/dt-bindings/mailbox/qcom-ipcc.h
+++ b/include/dt-bindings/mailbox/qcom-ipcc.h
@@ -36,4 +36,65 @@
#define IPCC_CLIENT_GPDSP0 31
#define IPCC_CLIENT_GPDSP1 32
+/* Platform specific physical client IDs */
+
+/* Glymur physical client IDs */
+#define GLYMUR_MPROC_AOP 0
+#define GLYMUR_MPROC_TZ 1
+#define GLYMUR_MPROC_MPSS 2
+#define GLYMUR_MPROC_LPASS 3
+#define GLYMUR_MPROC_SLPI 4
+#define GLYMUR_MPROC_SDC 5
+#define GLYMUR_MPROC_CDSP 6
+#define GLYMUR_MPROC_NPU 7
+#define GLYMUR_MPROC_APSS 8
+#define GLYMUR_MPROC_GPU 9
+#define GLYMUR_MPROC_ICP 11
+#define GLYMUR_MPROC_VPU 12
+#define GLYMUR_MPROC_PCIE0 13
+#define GLYMUR_MPROC_PCIE1 14
+#define GLYMUR_MPROC_PCIE2 15
+#define GLYMUR_MPROC_SPSS 16
+#define GLYMUR_MPROC_PCIE3 19
+#define GLYMUR_MPROC_PCIE4 20
+#define GLYMUR_MPROC_PCIE5 21
+#define GLYMUR_MPROC_PCIE6 22
+#define GLYMUR_MPROC_TME 23
+#define GLYMUR_MPROC_WPSS 24
+#define GLYMUR_MPROC_PCIE7 44
+#define GLYMUR_MPROC_SOCCP 46
+
+#define GLYMUR_COMPUTE_L0_LPASS 0
+#define GLYMUR_COMPUTE_L0_CDSP 1
+#define GLYMUR_COMPUTE_L0_APSS 2
+#define GLYMUR_COMPUTE_L0_GPU 3
+#define GLYMUR_COMPUTE_L0_CVP 6
+#define GLYMUR_COMPUTE_L0_ICP 7
+#define GLYMUR_COMPUTE_L0_VPU 8
+#define GLYMUR_COMPUTE_L0_DPU 9
+#define GLYMUR_COMPUTE_L0_SOCCP 11
+
+#define GLYMUR_COMPUTE_L1_LPASS 0
+#define GLYMUR_COMPUTE_L1_CDSP 1
+#define GLYMUR_COMPUTE_L1_APSS 2
+#define GLYMUR_COMPUTE_L1_GPU 3
+#define GLYMUR_COMPUTE_L1_CVP 6
+#define GLYMUR_COMPUTE_L1_ICP 7
+#define GLYMUR_COMPUTE_L1_VPU 8
+#define GLYMUR_COMPUTE_L1_DPU 9
+#define GLYMUR_COMPUTE_L1_SOCCP 11
+
+#define GLYMUR_PERIPH_LPASS 0
+#define GLYMUR_PERIPH_APSS 1
+#define GLYMUR_PERIPH_PCIE0 2
+#define GLYMUR_PERIPH_PCIE1 3
+#define GLYMUR_PERIPH_PCIE2 6
+#define GLYMUR_PERIPH_PCIE3 7
+#define GLYMUR_PERIPH_PCIE4 8
+#define GLYMUR_PERIPH_PCIE5 9
+#define GLYMUR_PERIPH_PCIE6 10
+#define GLYMUR_PERIPH_PCIE7 11
+#define GLYMUR_PERIPH_SOCCP 13
+#define GLYMUR_PERIPH_WPSS 16
+
#endif
--
2.34.1
next prev parent reply other threads:[~2025-09-24 18:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 18:37 [PATCH 0/5] dt-bindings: remoteproc: Document Glymur ADSP/CDSP PAS Sibi Sankar
2025-09-24 18:37 ` [PATCH 1/5] dt-bindings: mailbox: qcom-ipcc: Document the Glymur IPCC Sibi Sankar
2025-10-02 0:39 ` Rob Herring
2025-10-09 10:07 ` Sibi Sankar
2025-09-24 18:37 ` Sibi Sankar [this message]
2025-10-02 0:37 ` [PATCH 2/5] dt-bindings: mailbox: qcom-ipcc: Document Glymur physical client IDs Rob Herring
2025-09-24 18:37 ` [PATCH 3/5] dt-bindings: soc: qcom,aoss-qmp: Document the Glymur AOSS side channel Sibi Sankar
2025-09-24 18:37 ` [PATCH 4/5] dt-bindings: remoteproc: qcom,sm8550-pas: Document Glymur ADSP Sibi Sankar
2025-10-02 0:54 ` Rob Herring
2025-10-09 10:09 ` Sibi Sankar
2025-09-24 18:37 ` [PATCH 5/5] dt-bindings: remoteproc: qcom,sm8550-pas: Document Glymur CDSP Sibi Sankar
2025-10-02 0:55 ` Rob Herring (Arm)
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=20250924183726.509202-3-sibi.sankar@oss.qualcomm.com \
--to=sibi.sankar@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--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 \
/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