[PATCH] ARM: dts: broadcom: rpi: Switch to V3D firmware clock

[Stefan Wahren]

Hi Mark,

Am 27.10.25 um 13:07 schrieb Mark Brown:
> On Sun, Oct 26, 2025 at 01:40:19AM +0200, Stefan Wahren wrote:
>> Am 21.10.25 um 14:09 schrieb Mark Brown:
>>> I'm seeing the GPU start to fail probing on the Raspberry Pi 4 in
>>> today's pending-fixes:
>>> # # v3d fec00000.gpu: probe with driver v3d failed with error -110
>>> # not ok 1 +platform:fec00000.gpu
>>> which bisects to this commit.  I'm not sure if that's just a preexisting
>>> issue which is now being properly detected or if it's an actual issue,
>>> I'm not testing the GPU at all so I couldn't tell you if it was actually
>>> working.
>> can you confirm that this issue is fixed by this commit?
>> module: Fix device table module aliases [1]
>> [1] - https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20251024&id=9025688bf6d427e553aca911308cd92e92634f51
> No.  This is happening in mainline (was originally reported against
> pending-fixes) so wasn't affected by all the module breakage, that was
> separate.
I think, i got confused because I was only able to reproduce this issue 
with the broken linux-next. So I was going for the wrong cause :-(

Do you use arm64/defconfig as kernel config?
Is there a HDMI cable connected?

I noticed that you use an older raspberry-firmware. I will try to downgrade.

Best regards