From: Stephan Gerhold <stephan.gerhold@linaro.org>
To: Johan Hovold <johan+linaro@kernel.org>,
Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
Cc: 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>,
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: Wed, 16 Oct 2024 17:44:59 +0200 [thread overview]
Message-ID: <Zw_fe1tN_rdRR659@linaro.org> (raw)
In-Reply-To: <20241016145112.24785-1-johan+linaro@kernel.org>
On Wed, Oct 16, 2024 at 04:51:06PM +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
These look good to me, thanks!
Can you or Aleksandrs send another one for the x1e80100-dell-xps13-9345
that was applied by Bjorn yesterday?
FWIW, for these patches:
Reviewed-by: Stephan Gerhold <stephan.gerhold@linaro.org>
>
>
> 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
>
> arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dts | 2 ++
> arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts | 2 ++
> arch/arm64/boot/dts/qcom/x1e80100-crd.dts | 2 ++
> arch/arm64/boot/dts/qcom/x1e80100-lenovo-yoga-slim7x.dts | 2 ++
> arch/arm64/boot/dts/qcom/x1e80100-microsoft-romulus.dtsi | 2 ++
> arch/arm64/boot/dts/qcom/x1e80100-qcp.dts | 2 ++
> 6 files changed, 12 insertions(+)
>
> --
> 2.45.2
>
next prev parent reply other threads:[~2024-10-16 15:45 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 ` Stephan Gerhold [this message]
2024-10-16 15:52 ` [PATCH 0/6] arm64: dts: qcom: x1e80100: " 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=Zw_fe1tN_rdRR659@linaro.org \
--to=stephan.gerhold@linaro.org \
--cc=abel.vesa@linaro.org \
--cc=alex.vinarskis@gmail.com \
--cc=andersson@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.