From: Amir Hanip <killdeath104@gmail.com>
To: andersson@kernel.org, konradybcio@kernel.org,
linux-arm-msm@vger.kernel.org
Cc: abelvesa@kernel.org, conor+dt@kernel.org,
devicetree@vger.kernel.org, killdeath104@gmail.com,
krzk+dt@kernel.org, linux-kernel@vger.kernel.org,
robh@kernel.org, barnabas.czeman@mainlining.org,
a39skl@gmail.com, konrad.dybcio@oss.qualcomm.com,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: [PATCH v3 1/3] dt-bindings: arm: qcom: Document Xiaomi Poco M3
Date: Sat, 7 Nov 2026 21:14:30 +0700 [thread overview]
Message-ID: <20261107141432.39099-2-killdeath104@gmail.com> (raw)
In-Reply-To: <20261107141432.39099-1-killdeath104@gmail.com>
Add compatible for Xiaomi Poco M3 codename citrus, which is
based on Snapdragon 662 (SM6115) SoC.
Signed-off-by: Amir Hanip <killdeath104@gmail.com>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
---
Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
index 121ca557ce..8d2e4f0e34 100644
--- a/Documentation/devicetree/bindings/arm/qcom.yaml
+++ b/Documentation/devicetree/bindings/arm/qcom.yaml
@@ -1068,6 +1068,7 @@ properties:
- items:
- enum:
- fxtec,pro1x
+ - xiaomi,citrus
- xiaomi,lemon
- const: qcom,sm6115
--
2.47.3
next prev parent reply other threads:[~2026-11-07 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 14:14 [PATCH v3 0/3] arm64: dts: qcom: Add Xiaomi Poco M3 (citrus) Amir Hanip
2026-11-07 14:14 ` Amir Hanip [this message]
2026-11-07 14:14 ` [PATCH v3 2/3] arm64: dts: qcom: sm6115-xiaomi-lemon: Split out a common dtsi Amir Hanip
2026-11-07 17:49 ` Barnabás Czémán
2026-11-07 14:14 ` [PATCH v3 3/3] arm64: dts: qcom: Add Xiaomi Poco M3 Amir Hanip
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=20261107141432.39099-2-killdeath104@gmail.com \
--to=killdeath104@gmail.com \
--cc=a39skl@gmail.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=barnabas.czeman@mainlining.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--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®