From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Stefan Wahren <wahrenst@gmx.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Cc: bcm-kernel-feedback-list@broadcom.com, kernel-dev@igalia.com,
Ulf Hansson <ulf.hansson@linaro.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-arm-kernel@lists.infradead.org,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] arm64: defconfig: Fix V3D deferred probe timeout
Date: Tue, 4 Nov 2025 14:20:59 -0800 [thread overview]
Message-ID: <55c23802-e545-4e88-9814-8d24fd24815c@broadcom.com> (raw)
In-Reply-To: <20251104174518.11783-1-wahrenst@gmx.net>
On 11/4/25 09:45, Stefan Wahren wrote:
> The commit 4adc20ba95d4 ("ARM: dts: broadcom: rpi: Switch to V3D firmware
> clock") causes a regression in arm64 developer setups, which stores the
> kernel modules via NFS. Before this change the involved V3D clock provider
> was builtin, but after this DT change the clk-raspberrypi is responsible
> for V3D and for arm64/defconfig this driver is build as a kernel module.
> In case these kernel modules are provided via NFS this takes too long and
> the PM domain core give up before the clock driver could be loaded:
>
> v3d fec00000.gpu: deferred probe timeout, ignoring dependency
>
> So resolve this issue by making this critical driver builtin.
>
> Reported-by: Mark Brown <broonie@kernel.org>
> Closes: https://lore.kernel.org/linux-arm-kernel/9ebda74e-e700-4fbe-bca5-382f92417a9c@sirena.org.uk/
> Fixes: 4adc20ba95d4 ("ARM: dts: broadcom: rpi: Switch to V3D firmware clock")
> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
Applied, thanks Stefan!
--
Florian
next prev parent reply other threads:[~2025-11-04 22:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 17:45 [PATCH] arm64: defconfig: Fix V3D deferred probe timeout Stefan Wahren
2025-11-04 22:20 ` Florian Fainelli [this message]
2025-11-12 17:20 ` Stefan Wahren
2025-11-16 13:52 ` Mark Brown
2025-11-16 17:14 ` Florian Fainelli
2025-11-16 17:56 ` Mark Brown
2025-11-17 8:04 ` Krzysztof Kozlowski
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=55c23802-e545-4e88-9814-8d24fd24815c@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-dev@igalia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=m.szyprowski@samsung.com \
--cc=ulf.hansson@linaro.org \
--cc=wahrenst@gmx.net \
--cc=will@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.