drm_object_...ty_set_value(9)

💅 drm_object_...ty_set_value(9) — Kernel API Manual 🎀

okay so bestie, this page lives in the Kernel API Manual and we're talking about drm_object_property_set_value. it's giving very "one job, does it well" energy, and honestly? we love her for it ✨

---

✨ NAME ✨

drm_object_property_set_value — set the value of a property 🫶

---

🌸 SYNOPSIS 🌸

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

---

🦋 ARGUMENTS 🦋

• obj — the drm mode object you're setting a property value on 💖
• property — the property itself, like, the thing being set
• val — the value the property should be set to. the moment of truth, no cap

---

👑 DESCRIPTION 👑

so here's the tea: this function sets a given property on a given object. that's the whole vibe 🎀

but — and this is the important part — it only changes the software state of the property. it does not call into the driver's ->set_property callback. like, at all. it's just bookkeeping, bestie 😭

note that atomic drivers should not have any need to call this. the core will ensure consistency of values reported back to userspace through the appropriate ->atomic_get_property callback. only legacy drivers should call this function to update the tracked value (after clamping and other restrictions have been applied). so if you're on atomic and you're reaching for this, like… why 💀

---

⭐ RETURN ⭐

zero on success 🎉, error code on failure 😔

---

🌈 SEE ALSO 🌈

kernel file ./drivers/gpu/drm/drm_mode_object.c — go read it, iykyk 🧚

• drm_mode_object_add(9)
• drm_mode_object_unregister(9)
• drm_mode_object_lease_required(9)
• drm_mode_object_find(9)
• drm_mode_object_put(9)
• drm_mode_object_get(9)
• drm_object_attach_property(9)
• drm_object_property_get_value(9)
• drm_object_property_get_default_value(9)
• drm_object_immutable_property_get_value(9)
• drm_mode_obj_get_properties_ioctl(9)

---

and that's the whole page, bestie 💜 this one came from the ./drivers/gpu/drm era, dated October 2026, and yes the header up top still says drm_object_...ty_set_value(9) because the terminal is doing its little truncation thing 🙈 slay, go set some property values (legacy-style, not atomic, i'm begging) 🫶