drm_object_...ty_get_value(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ drm_object_property_get_value(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸ’– this one's a lil function from the DRM core and it's literally the "hey what's this property set to rn" girlie. let's get into it πŸŽ€


🌸 NAME 🌸

drm_object_property_get_value β€” retrieve the value of a property πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int drm_object_property_get_value (struct drm_mode_object *obj ,
                                   struct drm_property *property ,
                                   uint64_t *val );

✨ ARGUMENTS ✨

  • obj β€” the drm mode object you're pulling the property value from 🫢
  • property β€” the property you wanna retrieve, iykyk
  • val β€” your storage spot where the property value gets dropped off πŸ“¦

πŸ’œ DESCRIPTION πŸ’œ

so this function retrieves the software state of the given property for the given property β€” yes bestie, that's exactly what it says, it's a lil goofy but we move πŸ˜­πŸ’€

the big thing here: there's no driver callback to retrieve the current property value, so what you get back might be out of sync with the hardware β€” and that totally depends upon the driver and the property. so like… vibe check your expectations, ngl πŸ™ˆ

atomic drivers: do NOT call this function directly, periodt. the core will read out property values through the various ->atomic_get_property callbacks instead. that's the main character behavior, not yours πŸ’…πŸ‘‘

πŸ”₯ RETURN πŸ”₯

  • Zero on success πŸŽ‰
  • an error code on failure 😭

🌈 SEE ALSO 🌈

kernel file ./drivers/gpu/drm/drm_mode_object.c and its whole friend group:


okay that's the whole page, no cap πŸ§šπŸ’– this lil icon lives in ./drivers/gpu/drm, dated October 2026, and it's serving drm_object_...ty_get_value(9) energy from the Kernel API Manual. slay, go read your property values responsibly πŸŽ€β­πŸ«Ά

πŸ“¦ where this page comes from