From: Mark Brown <broonie@kernel.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
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,
Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>
Subject: Re: [PATCH] arm64: defconfig: Fix V3D deferred probe timeout
Date: Sun, 16 Nov 2025 13:52:51 +0000 [thread overview]
Message-ID: <aRnXMzuxPXfmRf30@sirena.co.uk> (raw)
In-Reply-To: <cbb49407-5b66-409d-8a0b-260e50932156@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On Wed, Nov 12, 2025 at 06:20:38PM +0100, Stefan Wahren wrote:
> Am 04.11.25 um 18:45 schrieb Stefan Wahren:
> > 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.
> can you confirm, that this fixes the problem in your case?
Yes, it seems to work. Given that this patch was applied I had been
expecting it to show up in -next but that doesn't seem to be the case?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-11-16 13:53 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
2025-11-12 17:20 ` Stefan Wahren
2025-11-16 13:52 ` Mark Brown [this message]
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=aRnXMzuxPXfmRf30@sirena.co.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=florian.fainelli@broadcom.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.