STRUCT DRM_WRITEBACK_JOB(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ 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 β€” a bool that gets set when the job has been prepared with drm_writeback_prepare_job ✨ so like, it's the little flag that says "yep, we're prepped."
  • cleanup_work β€” a struct work_struct that exists so drm_writeback_signal_completion can defer dropping the framebuffer reference onto a workqueue 🧚 lowkey iconic delegation behavior.
  • list_entry β€” the list item for the writeback connector's job_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, use drm_writeback_set_fb instead. 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.h struct drm_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