ENUM TTM_OBJECT_TYPE(9)

🌸 NAME 🌸

enum ttm_object_type — the name line has a little dash and then absolutely nothing else, bestie 😭 that's the whole NAME description.

✨ SYNOPSIS ✨

Okay so the enum is giving exactly this:

enum ttm_object_type {
    ttm_fence_type ,
    ttm_lock_type ,
    ttm_prime_type ,
    ttm_driver_type0 ,
    ttm_driver_type1 ,
    ttm_driver_type2 ,
    ttm_driver_type3 ,
    ttm_driver_type4 ,
    ttm_driver_type5

};

🎀 Constants 🎀

The original page labels every single one of these -- undescribed --, so we are not inventing lore. Here's the full set, all nine, no skips:

• ttm_fence_type — -- undescribed -- (the page literally leaves it a mystery 🙈)
• ttm_lock_type — -- undescribed -- (again, no description in the original)
• ttm_prime_type — -- undescribed -- (mystery era continues)
• ttm_driver_type0 — -- undescribed -- (no extra deets given)
• ttm_driver_type1 — -- undescribed -- (same energy)
• ttm_driver_type2 — -- undescribed -- (still keeping it mysterious)
• ttm_driver_type3 — -- undescribed -- (the page said what it said)
• ttm_driver_type4 — -- undescribed -- (no description here either)
• ttm_driver_type5 — -- undescribed -- (and that's the last one, iconic)

💖 Description 💖

Real talk: one entry per ttm object type. Device-specific types should use the ttm_driver_typex types. That's the whole description, short and slay ✨

🦋 SEE ALSO 🦋

Go read these next, bestie:

• Kernel file ./drivers/gpu/drm/vmwgfx/ttm_object.h
• struct ttm_base_object(9)
• struct ttm_prime_object(9)
• ttm_base_object_init(9)
• ttm_base_object_lookup(9)
• ttm_base_object_lookup_for_ref(9)
• ttm_base_object_unref(9)
• ttm_ref_object_base_unref(9)
• ttm_object_file_init(9)
• ttm_object_file_release(9)
• ttm_object_device_release(9)

Byeee 💅 source ./drivers/gpu/drm/vmwgfx, date October 2026, from the Kernel API Manual — enum ttm_object_type(9) out, mwah 🫶