From: sashiko-bot@kernel.org
To: "Jens Glathe" <jens.glathe@oldschoolsolutions.biz>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 5/7] arm64: dts: qcom: ideacentre-mini: Fix the second M.2 3V3 rail
Date: Sat, 05 Sep 2026 09:36:07 +0000 [thread overview]
Message-ID: <20260905093608.2DBF51F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260905-x1-ideacentre-mini-prettify-v1-5-9a87882973bb@oldschoolsolutions.biz>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Encoding a consumer (M.2 NVMe) power-up delay into the provider (regulator) DT node as 'startup-delay-us' violates Device Tree design principles.
--
commit 74fe38037d977753f0083d520b231c28126f164d
Author: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
arm64: dts: qcom: ideacentre-mini: Fix the second M.2 3V3 rail
This commit switches the vreg_nvme2_3p3 regulator to the PMIC GPIO and adds a
2-second startup delay along with an always-on property to work around M.2
probing failures.
> diff --git a/arch/arm64/boot/dts/qcom/x1-lenovo-ideacentre-mini-01q8x10.dtsi b/arch/arm64/boot/dts/qcom/x1-lenovo-ideacentre-mini-01q8x10.dtsi
> --- a/arch/arm64/boot/dts/qcom/x1-lenovo-ideacentre-mini-01q8x10.dtsi
> +++ b/arch/arm64/boot/dts/qcom/x1-lenovo-ideacentre-mini-01q8x10.dtsi
[ ... ]
> @@ -173,13 +174,16 @@ vreg_nvme2_3p3: regulator-nvme2-3p3 {
> regulator-min-microvolt = <3300000>;
> regulator-max-microvolt = <3300000>;
>
> - gpio = <&tlmm 18 GPIO_ACTIVE_HIGH>;
> + gpio = <&pmc8380_3_gpios 5 GPIO_ACTIVE_HIGH>;
> enable-active-high;
>
> - pinctrl-0 = <&nvme_reg_en>;
> + pinctrl-0 = <&nvme2_reg_en>;
> pinctrl-names = "default";
>
> + startup-delay-us = <2000000>;
[Severity: Medium]
Does adding startup-delay-us to the regulator node violate Device Tree design
principles by encoding a software workaround for the consumer's (M.2 NVMe)
initialization time?
Device Tree serves as a hardware description and stable ABI. Encoding a
2,000,000 us (2 seconds) delay here describes the consumer's initialization
time, rather than the physical stabilization time of the regulator hardware.
Once a proper M.2 PCIe power sequencer driver is introduced, will this node
continue to force the regulator framework to needlessly block for 2 seconds
whenever the regulator is enabled?
> +
> regulator-boot-on;
> + regulator-always-on;
> };
>
> vreg_v0p9: regulator-v0p9 {
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260905-x1-ideacentre-mini-prettify-v1-0-9a87882973bb@oldschoolsolutions.biz?part=5
next prev parent reply other threads:[~2026-09-05 9:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-05 9:28 [PATCH 0/7] arm64: dts: qcom: IdeaCentre Mini 01Q8X10 Hamoa + Purwa Jens Glathe via B4 Relay
2026-09-05 9:28 ` [PATCH 1/7] dt-bindings: arm: qcom: Distinguish IdeaCentre Mini 01Q8X10 SKUs Jens Glathe via B4 Relay
2026-09-05 9:28 ` [PATCH 2/7] arm64: dts: qcom: Split IdeaCentre Mini into a common DTSI Jens Glathe via B4 Relay
2026-09-05 9:28 ` [PATCH 3/7] arm64: dts: qcom: Add Purwa IdeaCentre Mini 01Q8X10 Jens Glathe via B4 Relay
2026-09-05 9:42 ` sashiko-bot
2026-09-05 10:46 ` Jens Glathe
2026-09-05 9:28 ` [PATCH 4/7] arm64: dts: qcom: ideacentre-mini: Build the Hamoa EL2 DTB Jens Glathe via B4 Relay
2026-09-05 9:29 ` [PATCH 5/7] arm64: dts: qcom: ideacentre-mini: Fix the second M.2 3V3 rail Jens Glathe via B4 Relay
2026-09-05 9:36 ` sashiko-bot [this message]
2026-09-05 9:29 ` [PATCH 6/7] arm64: dts: qcom: ideacentre-mini: Wire up DP sound names and VA macro Jens Glathe via B4 Relay
2026-09-05 9:29 ` [PATCH 7/7] arm64: dts: qcom: ideacentre-mini: Drop the unused USB MP port Jens Glathe via B4 Relay
2026-09-05 9:39 ` 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=20260905093608.2DBF51F00A3D@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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