From: Johan Hovold <johan+linaro@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Abel Vesa <abel.vesa@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>,
stable@vger.kernel.org
Subject: [PATCH 2/6] arm64: dts: qcom: x1e80100-crd: fix nvme regulator boot glitch
Date: Wed, 16 Oct 2024 16:51:08 +0200 [thread overview]
Message-ID: <20241016145112.24785-3-johan+linaro@kernel.org> (raw)
In-Reply-To: <20241016145112.24785-1-johan+linaro@kernel.org>
The NVMe regulator has been left enabled by the boot firmware. Mark it
as such to avoid disabling the regulator temporarily during boot.
Fixes: eb57cbe730d1 ("arm64: dts: qcom: x1e80100: Describe the PCIe 6a resources")
Cc: stable@vger.kernel.org # 6.11
Cc: Abel Vesa <abel.vesa@linaro.org>
Signed-off-by: Johan Hovold <johan+linaro@kernel.org>
---
arch/arm64/boot/dts/qcom/x1e80100-crd.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/x1e80100-crd.dts b/arch/arm64/boot/dts/qcom/x1e80100-crd.dts
index 10b28d870f08..5d2eec8590ce 100644
--- a/arch/arm64/boot/dts/qcom/x1e80100-crd.dts
+++ b/arch/arm64/boot/dts/qcom/x1e80100-crd.dts
@@ -300,6 +300,8 @@ vreg_nvme: regulator-nvme {
pinctrl-names = "default";
pinctrl-0 = <&nvme_reg_en>;
+
+ regulator-boot-on;
};
vreg_wwan: regulator-wwan {
--
2.45.2
next prev parent reply other threads:[~2024-10-16 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 14:51 [PATCH 0/6] arm64: dts: qcom: x1e80100: fix nvme regulator boot glitch Johan Hovold
2024-10-16 14:51 ` [PATCH 1/6] arm64: dts: qcom: x1e78100-t14s: " Johan Hovold
2024-10-16 14:51 ` Johan Hovold [this message]
2024-10-16 14:51 ` [PATCH 3/6] arm64: dts: qcom: x1e80100-vivobook-s15: " Johan Hovold
2024-10-16 14:51 ` [PATCH 4/6] arm64: dts: qcom: x1e80100-yoga-slim7x: " Johan Hovold
2024-10-16 14:51 ` [PATCH 5/6] arm64: dts: qcom: x1e80100-microsoft-romulus: " Johan Hovold
2024-10-16 14:51 ` [PATCH 6/6] arm64: dts: qcom: x1e80100-qcp: " Johan Hovold
2024-10-16 15:44 ` [PATCH 0/6] arm64: dts: qcom: x1e80100: " Stephan Gerhold
2024-10-16 15:52 ` Aleksandrs Vinarskis
2024-10-18 0:33 ` Konrad Dybcio
2024-10-24 14:59 ` Bjorn Andersson
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=20241016145112.24785-3-johan+linaro@kernel.org \
--to=johan+linaro@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--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=robh@kernel.org \
--cc=stable@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