dpu_crtc_frame_event_cb(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dpu_crtc_frame_event_cb — the crtc frame event callback API

okay so real talk, bestie — this one lives in the Kernel API Manual, and it's basically the little doorbell 🔔 that says "hey, something happened on this crtc, go deal with it." Let's get into it.

✨ NAME ✨

dpu_crtc_frame_event_cb — the crtc frame event callback API, periodt. 💖

🎀 SYNOPSIS 🎀

void dpu_crtc_frame_event_cb (struct drm_crtc *crtc , u32 event );

like... that's it. that's the whole signature. she's cute, she's simple, she takes two things and returns nothing (void, obviously — no notes, she gives nothing back and that's iconic of her). 🦋

🌸 ARGUMENTS 🌸

  • crtc — Pointer to crtc. literally just a pointer to the crtc, bestie, that's the whole vibe. 🫶
  • event — Event to process. which event?? the one you're processing. iykyk. 👑

💅 DESCRIPTION 💅

okay so here's the tea ☕ — the encoder may call this for different events from different contexts. and by different contexts we mean like, IRQ, user thread, commit_thread, etc. so many vibes, so many places. 🌈

the way that each event needs to be carefully reviewed — like, do not just yolo this — and should be processed in the proper task context. why?? because otherwise you get a scheduling delay 😭 or you don't properly manage the irq context's bottom half processing. and nobody wants that. ngl that's the whole point.

🚨 bestie pls read this twice: the context you're in matters. IRQ context, user thread, commit_thread — they are NOT the same girlies and you cannot treat them the same. pick the right one or it's giving scheduling delay.

🔥 SEE ALSO 🔥

like go read the whole friend group, they're all connected fr fr 💜

🎀 mwah, that's the page! this lil' slice of the kernel lives over in ./drivers/gpu/drm/msm/disp/dpu1, and the version on the record is dated October 2026. slay, go process those events in the right context, ily, bye! 🌸✨💖

📦 where this page comes from