Repeated Binding of Display Controller (dc8200) in Kernel Logs – BeagleV Display Subsystem Issue?

BeagleV
1

Hello all,
I’m currently working on display bring-up and GUI rendering on a BeagleV platform. While checking the kernel logs during boot, I noticed repeated binding of the display controller dc8200 by the display subsystem, as shown below:

[ 10.074084] vs-drm display-subsystem: bound ffef600000.dc8200 (ops dc_component_ops)
[ 10.090664] vs-drm display-subsystem: bound ffef600000.dc8200 (ops dc_component_ops)
[ 10.138724] vs-drm display-subsystem: bound ffef600000.dc8200 (ops dc_component_ops)
…

This message is printed multiple times—more than 10 occurrences—in a short span of time in the kernel logs, and additionally, HDMI is not being detected on the target board.

If anyone has encountered this kind of issue before, could you please advise where I should start analyzing or debugging this repeated binding behavior?

2

Hello Balaji, and welcome to the Forum.

As with so many other analytic processes, it’s all about Context.
At 10 secs., I would assume it’s somewhere in the boot process after kernel handover,
so you need to start looking at what systemd is doing.

As I said in the start, it’s all about Context, so the surrounding events are going
to point you toward the interesting bits.

Can you see how we’re narrowing in the search already? :grinning:
Good luck!