drm_flip_work_queue(9)

💅 drm_flip_work_queue(9)

okay so bestie, welcome to the Kernel API Manual ✨ this one's a little kernel function called drm_flip_work_queue and honestly? she's a vibe. short, sweet, does exactly one thing. let's get into it 🎀

---

🌸 NAME

drm_flip_work_queue — queue work 🫶

like, literally just queue the work. that's the whole job. iconique behaviour tbh.

---

✨ SYNOPSIS

void drm_flip_work_queue (struct drm_flip_work *work , void *val );

no return value, no drama, just vibes and a void. 💜

---

🦋 ARGUMENTS

• work — the flip-work 🌈 this is the struct drm_flip_work * bestie, the whole little work-machinery situation you're feeding
• val — the value to queue 🍓 a void *, so it can be literally whatever you need it to be, and it gets handed back to you later. iykyk

---

👑 DESCRIPTION

Queues work — and like, "later" is doing some heavy lifting here, so let me be clear 💀 the work you queue does not run right away. it will later be run (passed back to drm_flip_func_t func) on a work queue after drm_flip_work_commit is called. so this is the "put it in the pile" step, not the "do it" step. no cap. 🔥

so the order of operations is giving:

1. you queue stuff with drm_flip_work_queue 🧚
2. it sits there, patiently, main character energy
3. you call drm_flip_work_commit
4. then it actually runs on the work queue and your func gets called 🎀

periodt. that's the whole flow 💅

---

⭐ SEE ALSO

• Kernel file ./drivers/gpu/drm/drm_flip_work.c — the source, go read her, she ate 🙈
• drm_flip_work_commit(9)
• drm_flip_work_init(9)
• drm_flip_work_cleanup(9)

like the whole little flip-work friend group honestly 🫶 go say hi to all of them.

---

heads up bestie: don't expect anything to happen until drm_flip_work_commit(9) shows up. queueing alone is just collecting, not running. ✨

---

and that's the page!! mwah 💖 this came out of ./drivers/gpu/drm and it's dated October 2026 — so like, future slay 🌸🦋 go queue something iconic, ily, bye!! 👑💜