mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Miguel Jesus Seron Gonzalez <info@gluon.es>
Cc: Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Dongjin Kim <tobetter@gmail.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: odroid-m1: keep vcc3v3_pcie enabled from boot
Date: Sun,  1 Nov 2026 23:16:09 +0100	[thread overview]
Message-ID: <179357136501.4108155.9270952989405440142.b4-ty@b4> (raw)
In-Reply-To: <20261019132458.855-1-info@gluon.es>


On Mon, 19 Oct 2026 15:24:58 +0200, Miguel Jesus Seron Gonzalez wrote:
> The 3.3V supply of the M.2 slot is a GPIO-controlled fixed regulator
> without regulator-boot-on. When the regulator driver probes, it
> requests the enable GPIO as low, cutting power to an NVMe drive that
> the bootloader has already powered up and used. When the PCIe
> controller is built in, it probes a few milliseconds later and
> re-enables the supply. The drive therefore sees a brief power glitch
> without enough time to fully discharge.
> 
> [...]

Applied, thanks!

[1/1] arm64: dts: rockchip: odroid-m1: keep vcc3v3_pcie enabled from boot
      commit: ff9ff0e5e40dde8e7d769c86d8314b37b323cac7

Best regards,
-- 
Heiko Stuebner <heiko@sntech.de>

      parent reply	other threads:[~2026-11-01 22:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 13:24 Miguel Jesus Seron Gonzalez
2026-10-19 19:27 ` Miguel Jesus Seron Gonzalez
2026-11-01 22:16 ` Heiko Stuebner [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=179357136501.4108155.9270952989405440142.b4-ty@b4 \
    --to=heiko@sntech.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=info@gluon.es \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.org \
    --cc=tobetter@gmail.com \
    /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

all inboxes | Powered by JetHome®