drm_fb_helper_hotplug_event(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– drm_fb_helper_hotplug_event(9) πŸ’–

okay so this is the Kernel API Manual page for drm_fb_helper_hotplug_event, and bestie it is literally the β€œnew screen just showed up, let’s figure out the vibe” function. no cap.


🌸 NAME 🌸

drm_fb_helper_hotplug_event β€” respond to a hotplug notification by probing all the outputs attached to the fb. πŸ’…

✨ SYNOPSIS ✨

int drm_fb_helper_hotplug_event (struct drm_fb_helper *fb_helper );

πŸŽ€ ARGUMENTS πŸŽ€

  • fb_helper β€” driver-allocated fbdev helper, can be NULL. πŸ™ˆ yes really, NULL is allowed.

πŸ¦‹ DESCRIPTION πŸ¦‹

Scan the connectors attached to the fb_helper and try to put together a setup after notification of a change in output configuration. it’s giving β€œnew monitor energy” but make it kernel. ✨

Called at runtime, takes the mode config locks to be able to check/change the modeset configuration.

🚨 real talk: must be run from process context (which usually means either the output polling work or a work item launched from the driver’s hotplug interrupt). don’t be weird about it.

Note that drivers may call this even before calling drm_fb_helper_initial_config but only after drm_fb_helper_init. This allows for a race-free fbcon setup and will make sure that the fbdev emulation will not miss any hotplug events. iconic, honestly. 🫢

πŸ”₯ RETURN πŸ”₯

0 on success and a non-zero error code otherwise. periodt. πŸ’―

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/drm_fb_helper.c, plus the whole fbdev helpers(9) friend group β€” go read these, iykyk:

okay bestie, that’s the whole page β€” signing off from ./drivers/gpu/drm, October 2026, on drm_fb_helper_hotplug_event(9). mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from