drm_kms_help...l_reschedule(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ drm_kms_helper_poll_reschedule ✨

okay so this is a page from the Kernel API Manual (drm_kms_helper_poll_reschedule(9)) and honestly? it's giving "small helper function, big responsibilities." let's get into it bestie πŸ’…


🌸 NAME 🌸

drm_kms_helper_poll_reschedule β€” reschedule the output polling work πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

void drm_kms_helper_poll_reschedule (struct drm_device *dev );

πŸ’– ARGUMENTS πŸ’–

  • dev β€” a drm_device, that's it, that's the whole argument list, iconic behavior fr fr πŸ‘‘

🌈 DESCRIPTION 🌈

So here's the tea β˜•: this function reschedules the output polling work, and it does that after polling for a connector has been enabled. like, the enabling happens first, then you reschedule. order matters, no cap.

Drivers must call this helper after enabling polling for a connector by setting the DRM_CONNECTOR_POLL_CONNECT / DRM_CONNECTOR_POLL_DISCONNECT flags in drm_connector::polled. yes, both flags, exactly those names, write them down πŸ“

and here's the lil plot twist 🫢 β€” if you disable polling by clearing those same flags for a connector, the output polling work will stop automatically if polling is disabled for all the other connectors too. so it's not just you turning it off, it's the whole friend group agreeing πŸ’€

⚠️ timing warning bestie: this function can be called only after polling has been enabled by calling drm_kms_helper_poll_init / drm_kms_helper_poll_enable. call it too early and that's on you πŸ™ˆ

πŸ”₯ SEE ALSO πŸ”₯

like, that's a whole syllabus, but every single one is linked for a reason πŸ’œ


and that's the whole page!! short, sweet, and fully booked πŸ“šβœ¨ this one lives over in ./drivers/gpu/drm, dated October 2026, and the header/footer will keep whispering drm_kms_helper_poll_reschedule(9) at you forever. stay polling, bestie 🌸🫢

πŸ“¦ where this page comes from