rpi: suspicious log messages from vc4_hdmi & raspberrypi-power

[Maíra Canal]

Hi Stefan,

On 03/09/26 16:19, Stefan Wahren wrote:
> Hi,
> while testing my old Raspberry Pi 3 B Plus with a mostly recent mainline 
> kernel, I noticed some suspicious messages in the log, which are new to 
> my eyes:
> 
> [    0.000000] Booting Linux on physical CPU 0x0
> [    0.000000] Linux version 7.2.0-14759-gf6ce17b2c3b2 (stern at schenker) 
> (arm-linux-gnueabihf-gcc (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0, GNU ld 
> (GNU Binutils for Ubuntu) 2.42) #60 SMP Thu Sep  3 20:31:50 CEST 2026
> [    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), 
> cr=10c5383d
> [    0.000000] CPU: div instructions available: patching division code
> [    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing 
> instruction cache
> [    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
> ...
> [    0.619485] raspberrypi-firmware firmware:rpi-firmware: Attached to 
> firmware from 2024-05-24T15:31:28
> ...
> NEW [   12.637746] raspberrypi-power firmware:rpi-firmware:power: 
> sync_state() pending due to 3f806000.vec
> NEW [   12.645164] raspberrypi-power firmware:rpi-firmware:power: 
> sync_state() pending due to 3f902000.hdmi
> NEW [   12.652442] raspberrypi-power firmware:rpi-firmware:power: 
> sync_state() pending due to 3fc00000.v3d
> ...
> [   28.835362] vc4-drm gpu: bound 3f400000.hvs (ops 0xbf2c6984)
> NEW [   28.839062] vc4_hdmi 3f902000.hdmi: DTS/ACPI name 'rx' not found, 
> legacy failed (-19)
> ...
> NEW [   28.879525] vc4_hdmi 3f902000.hdmi: Could not create device link 
> to hdmi-audio-codec.1.auto
> ...
> [   28.889098] input: vc4-hdmi HDMI Jack as /devices/platform/ 
> soc/3f902000.hdmi/sound/card0/input2
> ...
> [   28.901895] vc4-drm gpu: bound 3f902000.hdmi (ops 0xbf2c3fb8)
> [   28.902040] vc4-drm gpu: bound 3f806000.vec (ops 0xbf2c6498)
> [   28.902164] vc4-drm gpu: bound 3f004000.txp (ops 0xbf2c7720)
> [   28.902240] vc4-drm gpu: bound 3f206000.pixelvalve (ops 0xbf2c20ec)
> [   28.902323] vc4-drm gpu: bound 3f207000.pixelvalve (ops 0xbf2c20ec)
> [   28.902394] vc4-drm gpu: bound 3f807000.pixelvalve (ops 0xbf2c20ec)
> [   28.911383] vc4-drm gpu: bound 3fc00000.v3d (ops 0xbf2c7c54)
> 
> Is it worth to investigate or expected?

AFAIU these messages are harmless. From the documentation [1], "If
during the first attempt at calling sync_state() for a device, there are
still consumers that haven’t probed successfully, the sync_state() call
is postponed and reattempted in the future only when one or more
consumers of the device probe successfully."

Did you also observe issues during probing?

[1] https://docs.kernel.org/driver-api/driver-model/driver.html

Best regards,
- Maíra

> 
> Best regards