drm_plane_cr...ble_property(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_plane_create_zpos_immutable_property β€” the Kernel API Manual tea πŸ«–

okay so bestie, we're in the <pink>./drivers/gpu/drm</pink> section of the Kernel API Manual (October 2026 edition, iconic), and today's main character is drm_plane_create_zpos_immutable_property. yes the name is a whole mouthful, no I will not be shortening it, periodt. ✨


🌸 NAME 🌸

drm_plane_create_zpos_immutable_property β€” create immuttable zpos property πŸ’…

not me pointing out that the original literally spells it "immuttable" β€” that's canon, we keep it, iykyk 😭

πŸŽ€ SYNOPSIS πŸŽ€

int drm_plane_create_zpos_immutable_property (struct drm_plane *plane ,
       unsigned int zpos );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • plane β€” drm plane. the plane in question, the literal subject of the whole function, she's that girl 🫢
  • zpos β€” value of zpos property. like, the actual number you're setting it to πŸ”₯

πŸ’– DESCRIPTION πŸ’–

okay so what does this function actually do? it initializes the generic immutable zpos property and enables support for it in drm core. that's the whole vibe check βœ…

using this property driver lets userspace get the arrangement of the planes for blending operation, and it also notifies userspace that the hardware (or driver) does not support changing of the planes' order. read that again β€” immutable, bestie, no take-backsies, the order is locked in πŸ”’

if you're out here wanting a mutable zpos instead, go see drm_plane_create_zpos_property. that one's the flexible sibling πŸ’œ

the property exposed to userspace is called "zpos". that's it. that's the name. slay ✨


⭐ RETURN ⭐

  • Zero on success πŸŽ‰
  • negative errno on failure 😭

πŸ‘‘ SEE ALSO πŸ‘‘

like, go read them, they're all literally right there, the whole friend group 🌈


that's the whole page bestie!! this one came from the ./drivers/gpu/drm section, dated October 2026 β€” mwah, love u, go read the kernel docs πŸ’‹πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from