drm_fb_dma_s...non_coherent(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_fb_dma_s...non_coherent(9) β€” Kernel API Manual, section 9

okay so bestie, welcome to the glow-up era of this lil kernel API page ✨ this one lives in the Kernel API Manual, section 9, and it's genuinely so niche but so real.


πŸŽ€ NAME πŸŽ€

drm_fb_dma_sync_non_coherent β€” sync a GEM object to non-coherent backing memory. that's it, that's the whole vibe 🫢


✨ SYNOPSIS ✨

void drm_fb_dma_sync_non_coherent (struct drm_device *drm , struct
drm_plane_state *old_state , struct drm_plane_state *state );

no cap, that's the exact signature, character for character πŸ’…


🌸 ARGUMENTS 🌸

  • drm β€” the DRM device. your main character, lowkey πŸ‘‘
  • old_state β€” the old plane state. the before pic πŸ™ˆ
  • state β€” the new plane state. the after pic ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so here's the tea: this function is for drivers that use damage clips and have DMA GEM objects backed by non-coherent memory. very specific combo, we love a niche icon πŸ’–

call this function in a plane's .atomic_update and it makes sure that all the data in the backing memory has been written to RAM. literally that's the whole job, and it ate πŸ”₯


🌈 SEE ALSO 🌈

iykyk, go read the whole friend group πŸ’œ


⭐ reminder: the behaviour above is exactly what the page says β€” no extra lore, no invented tips, fr fr.

and that's a wrap, bestie πŸŽ€ this page belongs to ./drivers/gpu/drm, dated October 2026, filed under drm_fb_dma_s...non_coherent(9) β€” mwah, periodt πŸ’…πŸŒŸ

πŸ“¦ where this page comes from