From: Dmitry Sinyavin <sinyavin@gmail.com>
To: Jassi Brar <jassisinghbrar@gmail.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] dt-bindings: mailbox: qcom: Add MDM9607 APCS IPC
Date: Tue, 8 Sep 2026 10:11:58 +0200 [thread overview]
Message-ID: <20260908081158.2399852-1-sinyavin@gmail.com> (raw)
The MDM9607 APCS IPC register is at offset 0x8 in the KPSS global block.
Its CPU clock controller is in a separate block, so the existing MSM8994
APCS match data can be used without registering a clock device.
Document the MDM9607 compatible with the MSM8994 fallback so the existing
driver match data can be reused.
Signed-off-by: Dmitry Sinyavin <sinyavin@gmail.com>
---
Validated with dt_binding_check, including yamllint, and positive and
negative DTB tests for the compatible string combination. Existing
MSM8974, MSM8976 and MSM8994 APCS nodes also pass schema validation.
Built the APCS IPC driver for ARM (multi_v7_defconfig) and arm64 (defconfig)
with Clang and W=1.
.../devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml b/Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml
index 39bc374300c3..e87373054d76 100644
--- a/Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml
+++ b/Documentation/devicetree/bindings/mailbox/qcom,apcs-kpss-global.yaml
@@ -33,6 +33,7 @@ properties:
- const: syscon
- items:
- enum:
+ - qcom,mdm9607-apcs-kpss-global
- qcom,msm8974-apcs-kpss-global
- qcom,msm8976-apcs-kpss-global
- const: qcom,msm8994-apcs-kpss-global
base-commit: 14af7a96afa39f4f3c1972705489b9ba15c01857
next reply other threads:[~2026-09-08 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 8:11 Dmitry Sinyavin [this message]
2026-09-08 11:02 ` Konrad Dybcio
2026-09-10 11:23 ` Dmitry Sinyavin
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=20260908081158.2399852-1-sinyavin@gmail.com \
--to=sinyavin@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jassisinghbrar@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®