mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Igor Velkov <iav@iav.lv>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Igor Velkov <iav@iav.lv>
Subject: Re: [PATCH] arm64: dts: rockchip: Add the GPU to Kobol Helios64
Date: Sat, 31 Oct 2026 01:00:00 +0200	[thread overview]
Message-ID: <20261031-helios64-gpu-always-on-1@iav.lv> (raw)
In-Reply-To: <1937939.QCnGb9OGeP@phil>

On Fri, 30 Oct 2026 20:29:47 +0100, Heiko Stuebner wrote:
> > +		regulator-always-on;
> > +		regulator-boot-on;
>
> both of these should not be needed, as the GPU should control its
> regulator. (always-on and boot-on)

Without them it breaks on this board (v7.3):
- with panfrost not loaded, the regulator core turns vdd_gpu off 30 s
  after boot and the next warm reboot hangs in the DDR init (TPL, DDR
  blob v1.25, at "change freq to 856MHz"), 2 of 2; only removing power
  recovers it. All 119 boots in my console log passed there with the
  rail on.
- panfrost loaded after that: "failed to get ack on domain 'gpu'", the
  GPU stays deferred, since pd_gpu powers up before mali-supply is on.
So I would keep always-on and boot-on, as the other RK3399 boards do.

      reply	other threads:[~2026-10-30 22:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10 21:53 Igor Velkov via B4 Relay
2026-10-30 19:29 ` Heiko Stuebner
2026-10-30 23:00   ` Igor Velkov [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=20261031-helios64-gpu-always-on-1@iav.lv \
    --to=iav@iav.lv \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --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 \
    /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®