STRUCT DRM_WRITEBACK_JOB(9)
β¨ struct drm_writeback_job(9) β¨
okay so bestie, this is the Kernel API Manual entry for struct drm_writeback_job β literally the DRM writeback job itself π
it's the lil struct that holds everything a writeback connector needs to know about a job, and we're gonna go through every single member, no skipping, periodt.
π¦ SYNOPSIS π¦
struct drm_writeback_job {
struct drm_writeback_connector *connector;
bool prepared;
struct work_struct cleanup_work;
struct list_head list_entry;
struct drm_framebuffer *fb;
struct dma_fence *out_fence;
void *priv;
};
π Members π
connectorβ back-pointer to the writeback connector that this job belongs to π«Ά it's giving "know your roots" energy, iykyk.preparedβ aboolthat gets set when the job has been prepared withdrm_writeback_prepare_jobβ¨ so like, it's the little flag that says "yep, we're prepped."cleanup_workβ astruct work_structthat exists sodrm_writeback_signal_completioncan defer dropping the framebuffer reference onto a workqueue π§ lowkey iconic delegation behavior.list_entryβ the list item for the writeback connector'sjob_queueπ it's how the job hangs out in the queue with all its friends.fbβ the framebuffer that the writeback connector is gonna write to πΌοΈ but listen: do not set this directly, usedrm_writeback_set_fbinstead. no cap, don't touch it yourself.out_fenceβ the fence that will signal once the writeback has completed β like a little "we're done here!" notification.privβ driver-private data π whatever the driver wants to stash in there, it's all yours.
π SEE ALSO π
- Kernel file
./include/drm/drm_writeback.hstructdrm_writeback_connector(9)π¦
and that's the whole vibe check, bestie π this page came from ./include/drm, October 2026, and yes β it's still titled struct drm_writeback_job(9) at the very bottom too, slay πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms