From: Heiko Stuebner <heiko@sntech.de>
To: ulfh@kernel.org, Leonard Lausen <leonard@lausen.nl>
Cc: Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
detlev.casanova@collabora.com, finley.xiao@rock-chips.com,
zhangqing@rock-chips.com, inindev@gmail.com,
linux-pm@vger.kernel.org, gahing@gahingwoo.com
Subject: Re: (subset) [PATCH 0/2] Fix Panfrost boot hang on NanoPi M5
Date: Sun, 22 Nov 2026 23:50:26 +0100 [thread overview]
Message-ID: <179538782480.3150822.6529696700670964484.b4-ty@b4> (raw)
In-Reply-To: <20261019092417.391522-1-leonard@lausen.nl>
On Mon, 19 Oct 2026 09:24:14 +0000, Leonard Lausen wrote:
> On the NanoPi M5, boot hangs during Panfrost initialization. Before this
> fix, booting required blacklisting Panfrost on the kernel command line.
> Loading Panfrost after boot reports a GPU power-domain acknowledgment
> timeout.
>
> Enable regulator management for the RK3576 GPU power domain and connect
> its supply to the NanoPi M5 GPU rail.
>
> [...]
Applied, thanks!
[2/2] arm64: dts: rockchip: Fix GPU domain supply on NanoPi M5
commit: ac5f8e47fcb2e7a5e5829968a406d2fbff63db8b
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
prev parent reply other threads:[~2026-11-22 22:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 9:24 Leonard Lausen
2026-10-19 9:24 ` [PATCH 1/2] pmdomain: rockchip: Manage the RK3576 GPU domain supply Leonard Lausen
2026-10-19 10:05 ` Shawn Lin
2026-11-12 15:19 ` Ulf Hansson
2026-11-12 16:10 ` Leonard Lausen
2026-11-12 18:15 ` Sebastian Reichel
2026-11-13 17:47 ` Ulf Hansson
2026-11-12 18:12 ` Sebastian Reichel
2026-11-13 2:24 ` Finley Xiao
2026-10-19 9:24 ` [PATCH 2/2] arm64: dts: rockchip: Fix GPU domain supply on NanoPi M5 Leonard Lausen
2026-11-22 22:50 ` 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=179538782480.3150822.6529696700670964484.b4-ty@b4 \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=finley.xiao@rock-chips.com \
--cc=gahing@gahingwoo.com \
--cc=inindev@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=leonard@lausen.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=ulfh@kernel.org \
--cc=zhangqing@rock-chips.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®