From: Robert Eckelmann via B4 Relay <devnull+longnoserob.gmail.com@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
phone-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
david@ixit.cz, Robert Eckelmann <longnoserob@gmail.com>
Subject: [PATCH v3 3/3] arm64: dts: qcom: sdm845-xiaomi-beryllium: Add placeholders and sort
Date: Fri, 05 Dec 2025 22:59:01 +0900 [thread overview]
Message-ID: <20251205-slpi-v3-3-a1320a074345@gmail.com> (raw)
In-Reply-To: <20251205-slpi-v3-0-a1320a074345@gmail.com>
From: Robert Eckelmann <longnoserob@gmail.com>
We know these devices are present, most of them are supported by
downstream and close to the mainline kernels.
This is very handy when rebasing the integration tree with the support.
No functional changes.
Reviewed-by: David Heidelberg <david@ixit.cz>
Signed-off-by: Robert Eckelmann <longnoserob@gmail.com>
---
.../dts/qcom/sdm845-xiaomi-beryllium-common.dtsi | 29 ++++++++++++++++------
1 file changed, 22 insertions(+), 7 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-common.dtsi b/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-common.dtsi
index ab450d44b3f6..3444908b4a6b 100644
--- a/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-common.dtsi
+++ b/arch/arm64/boot/dts/qcom/sdm845-xiaomi-beryllium-common.dtsi
@@ -227,6 +227,12 @@ vreg_l26a_1p2: ldo26 {
};
};
+&cci_i2c0 {
+ status = "okay";
+
+ /* IMX363 @ 10 */
+};
+
&cdsp_pas {
status = "okay";
firmware-name = "qcom/sdm845/Xiaomi/beryllium/cdsp.mbn";
@@ -261,6 +267,22 @@ &ibb {
qcom,discharge-resistor-kohms = <300>;
};
+&ipa {
+ qcom,gsi-loader = "self";
+ memory-region = <&ipa_fw_mem>;
+ firmware-name = "qcom/sdm845/beryllium/ipa_fws.mbn";
+
+ status = "okay";
+};
+
+&i2c5 {
+ clock-frequency = <400000>;
+
+ status = "okay";
+
+ /* TAS2559 @ 4C */
+};
+
&lab {
regulator-min-microvolt = <4600000>;
regulator-max-microvolt = <6000000>;
@@ -312,13 +334,6 @@ &mss_pil {
"qcom/sdm845/Xiaomi/beryllium/modem.mbn";
};
-&ipa {
- qcom,gsi-loader = "self";
- memory-region = <&ipa_fw_mem>;
- firmware-name = "qcom/sdm845/Xiaomi/beryllium/ipa_fws.mbn";
- status = "okay";
-};
-
&pm8998_gpios {
vol_up_pin_a: vol-up-active-state {
pins = "gpio6";
--
2.52.0
next prev parent reply other threads:[~2025-12-05 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 13:58 [PATCH v3 0/3] arm64: dts: qcom: sdm845-xiaomi-beryllium: Enable SLPI Robert Eckelmann via B4 Relay
2025-12-05 13:58 ` [PATCH v3 1/3] " Robert Eckelmann via B4 Relay
2025-12-05 20:43 ` Dmitry Baryshkov
2025-12-05 13:59 ` [PATCH v3 2/3] arm64: dts: qcom: sdm845-xiaomi-beryllium: Adjust firmware paths Robert Eckelmann via B4 Relay
2025-12-05 20:43 ` Dmitry Baryshkov
2025-12-05 13:59 ` Robert Eckelmann via B4 Relay [this message]
2025-12-05 20:46 ` [PATCH v3 3/3] arm64: dts: qcom: sdm845-xiaomi-beryllium: Add placeholders and sort Dmitry Baryshkov
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=20251205-slpi-v3-3-a1320a074345@gmail.com \
--to=devnull+longnoserob.gmail.com@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longnoserob@gmail.com \
--cc=phone-devel@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;
as well as URLs for NNTP newsgroup(s).