CURSOR MODES - NATIVE VS OVERLAY(9)

💅 Cursor Modes - Native vs Overlay 💅

Okay bestie, this is from the Kernel API Manual (section 9), and we're doing the cursor-mode lore: native vs overlay. It's giving "two paths, very different vibes," and both details matter, so stay with me. ✨

Native mode, rise: in native mode, the cursor uses an integrated cursor pipe within each DCN hw plane. It does not require a dedicated hw plane to enable — slay — but it is subjected to the same z-order and scaling as the hw plane. It also has format restrictions: an RGB cursor in native mode cannot be enabled within a non-RGB hw plane. Not me being dramatic, that's just the rule, fr fr.

Overlay mode, main character energy: in overlay mode, the cursor uses a separate DCN hw plane, and thus has its own scaling and z-pos. It also has no blending restrictions. It lends to a cursor behavior more akin to a DRM client's expectations — honestly iconic. However, it does occupy an extra DCN plane, and therefore will only be used if a DCN plane is available. Plane availability is lowkey the whole plot twist. 🙈

🔍 SEE ALSO 🔍

• Kernel file ./drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_cursor.c — go read it, bestie, iykyk
• dm_plane_color_pipeline_active(9)
• amdgpu_dm_crtc_get_cursor_mode(9)

And that's the page, bestie! Kernel API Manual business, source ./drivers/gpu/drm/amd/display/..., dated October 2026 — mwah 💋✨