From: ShiTou Hong <redstone.dcity@gmail.com>
To: andersson@kernel.org, konradybcio@kernel.org, conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
ShiTou Hong <dc_redstone@outlook.com>,
KancyJoe <kancy2333@outlook.com>
Subject: [PATCH 4/6] arm64: dts: qcom: sm8250-hdk: Enable the PCIe ports
Date: Fri, 23 Oct 2026 15:28:30 +0800 [thread overview]
Message-ID: <20261023072832.2642647-4-dc_redstone@outlook.com> (raw)
In-Reply-To: <20261023072832.2642647-1-dc_redstone@outlook.com>
The sm8250-hdk has 2 PCIe ports which are not enabled in the dts.
The pcie0 is for the on-board ath11k WiFi/BT module;
while the pcie2 is for the M.2 connector.
Add the 3V3 regulator node for pcie2.
Enable the 2 pcie controllers and phys.
Co-developed-by: KancyJoe <kancy2333@outlook.com>
Signed-off-by: ShiTou Hong <dc_redstone@outlook.com>
---
arch/arm64/boot/dts/qcom/sm8250-hdk.dts | 28 +++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sm8250-hdk.dts b/arch/arm64/boot/dts/qcom/sm8250-hdk.dts
index 7a2903941..bd9b90fbc 100644
--- a/arch/arm64/boot/dts/qcom/sm8250-hdk.dts
+++ b/arch/arm64/boot/dts/qcom/sm8250-hdk.dts
@@ -57,6 +57,13 @@ lt9611_1v2: lt9611-vdd12-regulator {
regulator-max-microvolt = <1200000>;
};
+ vreg_3p3: vreg-3p3-regulator {
+ compatible = "regulator-fixed";
+ regulator-name = "vreg_3p3";
+ regulator-min-microvolt = <3300000>;
+ regulator-max-microvolt = <3300000>;
+ };
+
vreg_s6c_0p88: smpc6-regulator {
compatible = "regulator-fixed";
regulator-name = "vreg_s6c_0p88";
@@ -722,3 +729,24 @@ pm8150b_typec_sbu_out: endpoint {
&usb_1_qmpphy_dp_in {
remote-endpoint = <&mdss_dp_out>;
};
+
+&pcie0 {
+ status = "okay";
+};
+
+&pcie0_phy {
+ vdda-phy-supply = <&vreg_l5a_0p88>;
+ vdda-pll-supply = <&vreg_l9a_1p2>;
+ status = "okay";
+};
+
+&pcie2 {
+ status = "okay";
+ vddpe-3v3-supply = <&vreg_3p3>;
+};
+
+&pcie2_phy {
+ vdda-phy-supply = <&vreg_l5a_0p88>;
+ vdda-pll-supply = <&vreg_l9a_1p2>;
+ status = "okay";
+};
--
2.47.3
next prev parent reply other threads:[~2026-10-23 7:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 7:28 [PATCH 1/6] arm64: dts: qcom: sm8250-hdk: Enable the sdhc_2 port ShiTou Hong
2026-10-23 7:28 ` [PATCH 2/6] arm64: dts: qcom: sm8250-hdk: Add LT9611UXC HDMI bridge ShiTou Hong
2026-10-23 7:28 ` [PATCH 3/6] arm64: dts: qcom: sm8250-hdk: Add FSA4480 USB-C protocol chip ShiTou Hong
2026-10-23 7:51 ` sashiko-bot
2026-10-23 7:28 ` ShiTou Hong [this message]
2026-10-23 7:43 ` [PATCH 4/6] arm64: dts: qcom: sm8250-hdk: Enable the PCIe ports sashiko-bot
2026-10-23 7:28 ` [PATCH 5/6] arm64: dts: qcom: sm8250-hdk: Add support of QCA6390 ShiTou Hong
2026-10-23 7:28 ` [PATCH 6/6] arm64: dts: qcom: sm8250-hdk: Add PM8150b LEDs ShiTou Hong
-- strict thread matches above, loose matches on Subject: below --
2026-10-22 11:35 [PATCH 1/6] arm64: dts: qcom: sm8250-hdk: Enable the sdhc_2 port ShiTou Hong
2026-10-22 11:35 ` [PATCH 4/6] arm64: dts: qcom: sm8250-hdk: Enable the PCIe ports ShiTou Hong
2026-10-22 11:46 ` sashiko-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=20261023072832.2642647-4-dc_redstone@outlook.com \
--to=redstone.dcity@gmail.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dc_redstone@outlook.com \
--cc=devicetree@vger.kernel.org \
--cc=kancy2333@outlook.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.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