drm_helper_connector_dpms(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ drm_helper_connector_dpms ✨

Okay bestie, so we're looking at a page from the drm Helper Connector DPMS 9 manual, and honestly? It's giving legacy vibes but in a "we respect our elders" kind of way. Let me break it down for you πŸ’…


🌸 SYNOPSIS 🌸

int drm_helper_connector_dpms(struct drm_connector *connector, int mode);
Like, this is the whole vibe. Two args, one return, no cap.

πŸŽ€ ARGUMENTS πŸŽ€

  • connector β€” the affected connector, aka the main character of this whole situation
  • mode β€” the DPMS mode you're setting, periodt

πŸ’– DESCRIPTION πŸ’–

So the drm_helper_connector_dpms helper function implements the drm_connector_funcs.dpms callback for drivers that are using the legacy CRTC helpers. It's literally the go-to function for that whole setup πŸ”₯

This is the main helper function provided by the CRTC helper framework for implementing the DPMS connector attribute. Obsessed with that for it ✨ It computes the new desired DPMS state for all encoders and CRTCs in the output mesh (like, the whole squad gets a vibe check), and then it calls the drm_crtc_helper_funcs.dpms and drm_encoder_helper_funcs.dpms callbacks that the driver provides. Slay.

⚠️ Bestie, listen to me: this function is deprecated. Like, it's a legend and we respect it, but new drivers must implement atomic modeset support, where DPMS is handled in the DRM core. That's the future, honey, no cap πŸ’€

πŸ¦‹ RETURN πŸ¦‹

It always returns 0. Literally every single time. No surprises, no drama, just zero. Iconic consistency honestly 🫢


🌈 SEE ALSO 🌈

Here's the whole friend group, iykyk:


πŸ’œ Okay and like, this whole page lives at ./drivers/gpu/drm and it was dated October 2026, which is giving main character energy from the future or whatever. Anyway bestie, you got this! Go read those other manpages, muah πŸŽ€βœ¨πŸ’…
πŸ“¦ where this page comes from