From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Johan Hovold <johan+linaro@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
Subject: Re: [PATCH 0/6] arm64: dts: qcom: x1e80100: fix nvme regulator boot glitch
Date: Thu, 24 Oct 2024 09:59:29 -0500 [thread overview]
Message-ID: <172978197053.296432.10913188928059703345.b4-ty@kernel.org> (raw)
In-Reply-To: <20241016145112.24785-1-johan+linaro@kernel.org>
On Wed, 16 Oct 2024 16:51:06 +0200, Johan Hovold wrote:
> The NVMe regulator has been left enabled by the boot firmware. Mark it
> as such to avoid disabling the regulator temporarily during boot.
>
> Johan
>
>
> Johan Hovold (6):
> arm64: dts: qcom: x1e78100-t14s: fix nvme regulator boot glitch
> arm64: dts: qcom: x1e80100-crd: fix nvme regulator boot glitch
> arm64: dts: qcom: x1e80100-vivobook-s15: fix nvme regulator boot
> glitch
> arm64: dts: qcom: x1e80100-yoga-slim7x: fix nvme regulator boot glitch
> arm64: dts: qcom: x1e80100-microsoft-romulus: fix nvme regulator boot
> glitch
> arm64: dts: qcom: x1e80100-qcp: fix nvme regulator boot glitch
>
> [...]
Applied, thanks!
[1/6] arm64: dts: qcom: x1e78100-t14s: fix nvme regulator boot glitch
commit: dec19f1406fc5d73512cacdcf612e7bb161c2101
[2/6] arm64: dts: qcom: x1e80100-crd: fix nvme regulator boot glitch
commit: 37f9477ce9d07ed87f6efe9b99de580bc9d27df5
[3/6] arm64: dts: qcom: x1e80100-vivobook-s15: fix nvme regulator boot glitch
commit: c6d151f61b6703124e14bc0eae98d05206e36e02
[4/6] arm64: dts: qcom: x1e80100-yoga-slim7x: fix nvme regulator boot glitch
commit: 1badd07e4c0e1ecfb187dcba05357c0f3e70e797
[5/6] arm64: dts: qcom: x1e80100-microsoft-romulus: fix nvme regulator boot glitch
commit: 5462190b11aa62a945dc2fd74e1531b9c1bc9952
[6/6] arm64: dts: qcom: x1e80100-qcp: fix nvme regulator boot glitch
commit: 717f0637ffc6a6a59f838df94a7d61e643c98d62
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-10-24 14:59 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 ` [PATCH 2/6] arm64: dts: qcom: x1e80100-crd: " Johan Hovold
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 [this message]
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=172978197053.296432.10913188928059703345.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=abel.vesa@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan+linaro@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 \
/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