cmdq_pkt_acquire_event(9)

📦 version 7.3.1, in nixpkgs unstable

💅 cmdq_pkt_acquire_event(9) — a Kernel API Manual moment

okay bestie, welcome to the Kernel API Manual. This page is called cmdq_pkt_acquire_event and honestly it's serving serious "let me in, let me IN" energy.

✨ NAME ✨

cmdq_pkt_acquire_event — append an acquire event command to the CMDQ packet. That's it. That's the whole job. She appends, she acquires, she moves on. 🎀

🦋 SYNOPSIS 🦋

int cmdq_pkt_acquire_event (struct cmdq_pkt *pkt , u16 event );

Look at her. Two args, one int coming back. Simple, iconic, no notes. 💜

🌸 ARGUMENTS 🌸

  • pkt — the CMDQ packet. Like, the whole packet you're stuffing commands into. She's the container, she's the main character here.
  • event — the desired event to be acquired. A u16, so she's small but she matters. This is the thing you're waiting on, bestie.

👑 DESCRIPTION 👑

ok so here's the vibe: you can use cmdq_pkt_acquire_event as your mutex_lock, and cmdq_pkt_clear_event as your mutex_unlock, to protect some critical section instructions that live in between them. Dynamic duo fr fr. 🫶

Here's the part where you gotta pay attention (iykyk): cmdq_pkt_acquire_event would wait for the event to be cleared. It literally just sits there. Then — after that event gets cleared by cmdq_pkt_clear_event over in other GCE threads — cmdq_pkt_acquire_event would set the event and keep executing the next instruction. Like, respectfully, she waited her turn and now she's moving on. 😭✨

So the order is: wait for cleared → set it → next instruction. Do not skip steps, do not pass go. 💅

🔥 RETURN 🔥

  • 0 for success — slay 🎉
  • else the error code is returned — not slay, but at least you know 💀

🧚 SEE ALSO 🧚

Kernel file ./include/linux/soc/mediatek/mtk-cmdq.h — go read her, she's the source of truth.

and the whole friend group, no one left out:

and that's the page, bestie 🦋 — brought to you by ./include/linux/soc/mediatek, dated October 2026. bookmark it, cite it, live laugh lock. 💖

📦 where this page comes from