drm_client_m...ommit_locked(9)

💅 drm_client_m...ommit_locked — the Kernel API Manual, but make it make sense 💅

okay so bestie, welcome to drm_client_m...ommit_locked(9), a kernel API page that's gonna live in your brain rent-free. it's literally the "just do it" function for pushing a modeset config out to your CRTCs, no questions asked. let's get into it 🎀

---

✨ NAME ✨

drm_client_modeset_commit_locked — force commit that CRTC configuration, periodt 🔥

🌸 SYNOPSIS 🌸

int drm_client_modeset_commit_locked (struct drm_client_dev *client);

🦋 ARGUMENTS 🦋

• client — the DRM client, your main character for this whole operation 👑

🌈 DESCRIPTION 🌈

so here's the vibe: this commits the modeset configuration to the crtcs without checking whether there's a DRM master hanging around. no vibe check, no ID check at the door — it just goes.

the whole assumption (and yes, assumption is doing a lot of heavy lifting here, so listen up) is that you, the caller, already hold an internal DRM master reference that you acquired with drm_master_internal_acquire. so if you didn't do that? that's a you problem, bestie 😭 the lock is yours to bring, iykyk.

⭐ RETURN ⭐

• 0 (zero) on success — slay, it worked 💖
• a negative error code on failure — not slay, but at least it's honest 💀

💜 SEE ALSO 💜

kernel file ./drivers/gpu/drm/drm_client_modeset.c — the actual source, go read it fr fr

• drm_client_modeset_probe(9)
• drm_client_rotation(9)
• drm_client_modeset_check(9)
• drm_client_modeset_commit(9)
• drm_client_modeset_dpms(9)
• drm_client_modeset_wait_for_vblank(9)

---

and that's the whole page, bestie — go forth and commit responsibly 🫶

this iconic little slice of kernel lore comes to you courtesy of ./drivers/gpu/drm, dropping October 2026 ✨📅 — save the date, mark your calendar, tell your friends 🧚