drm_writeba...l_completion(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– drm_writeback_signal_completion(9) β€” Kernel API Manual πŸ’–

okay so bestie, buckle up, because this one is from the Kernel API Manual and it's literally the "hey the hardware is done, tell everyone" function πŸŽ€


✨ NAME ✨

drm_writeback_signal_completion β€” signal the completion of a writeback job πŸ¦‹

like, the little bell you ring when the writeback job is officially done, no cap.


🌸 SYNOPSIS 🌸

void drm_writeback_signal_completion (struct drm_writeback_connector
*wb_connector , int status );

that's the whole vibe. void return, cutie β€” no coming back, no receipts. πŸ’…


🧚 ARGUMENTS 🧚

  • wb_connector β€” the writeback connector whose job is complete πŸ‘‘ like, this is the connector, the main character, the one who just finished.
  • status β€” the status code you're setting in the writeback out_fence. 0 means success πŸ’š (yes, zero is the good one here, iconic behaviour).

πŸ”₯ DESCRIPTION πŸ”₯

so drivers, listen up: you call this to signal the completion of a writeback job you queued earlier. it should be called ASAP after the hardware has finished writing β€” like, the instant, don't be shy β€” and it may be called from interrupt context 😭 (yes, from interrupt context, that's not a typo, that's just how it lives).

it is the driver's responsibility to make sure that, for a given connector, the hardware completes writeback jobs in the same order as they are queued. πŸ‘‘ order matters, periodt. no queue-jumping, no chaos, keep it in line.

πŸ’€ real talk warning: unless the driver is holding its own reference to the framebuffer, it must not be accessed after calling this function. like, do not touch it after. it's gone. respect the boundary 🫢

See also: drm_writeback_queue_job ✨ (the queuing half of the story, iykyk)


🌈 SEE ALSO 🌈

go read all of them, bestie, they're all linked, it's giving a whole ecosystem 🌸⭐


πŸ’œ mwah, that's the page πŸ’œ from ./drivers/gpu/drm, dated October 2026, in the Kernel API Manual β€” slay, bye πŸŽ€πŸ’…

πŸ“¦ where this page comes from