drm_gem_fb_afbc_init(9)

📦 version 7.3.1, in nixpkgs unstable

💅 drm_gem_fb_afbc_init(9) — the Kernel API Manual glow-up 🎀

okay so bestie, this page lives in the Linux Kernel API Manual and it's literally about drm_gem_fb_afbc_init — the helper function for drivers using afbc to fill and validate all the afbc-specific struct drm_afbc_framebuffer members. no cap, that's the whole name line, we love a function that tells you its job upfront. ✨

🌸 SYNOPSIS 🌸

int drm_gem_fb_afbc_init (struct drm_device *dev , const struct
drm_format_info *info , const struct drm_mode_fb_cmd2 *mode_cmd , struct
drm_afbc_framebuffer *afbc_fb );

🦋 ARGUMENTS 🦋

  • dev — the DRM device, your main character 🫶
  • info — pixel format information, aka the vibes of your pixels
  • mode_cmd — metadata from the userspace framebuffer creation request, like the receipt for what userspace asked you to build 🧾
  • afbc_fb — the afbc framebuffer itself 💖

🎀 DESCRIPTION 🎀

so this function is for drivers that support afbc and wanna finish prepping their struct drm_afbc_framebuffer. it's giving "last step, final touch, setting spray" 💅

important ordering note: it must be called after allocating the said struct and calling drm_gem_fb_init_with_funcs. no cutting the line, bestie, the sequence matters. ⭐

also, heads up: it is the caller's responsibility to put afbc_fb->base.obj objects in case the call is unsuccessful. like, if this whole thing flops, you're the one cleaning up the objects — no one's gonna do it for you, so don't ghost them 🙈

🔥 RETURN 🔥

Zero on success, or a negative error value on failure. that's it, that's the whole vibe check — 0 = slay, negative = not slay 😭

👑 SEE ALSO 👑

the whole framebuffer helper friend group, fr fr 🌈

and that's the page!! sourced from ./drivers/gpu/drm, dated October 2026, and yes the title of this little masterpiece is drm_gem_fb_afbc_init(9) — go forth and init your afbc framebuffers responsibly, bestie 💜🌸✨

📦 where this page comes from