STRUCT SSAM_DEVICE_UID(9)

🌸 struct ssam_device_uid(9) 🌸

okay bestie, welcome to the Kernel API Manual entry for struct ssam_device_uid ✨ it's giving “Unique identifier for SSAM device.” no cap, it's the little five-field vibe check for an SSAM device 🫶

💖 NAME 💖

struct ssam_device_uid — Unique identifier for SSAM device. periodt 💅

✨ SYNOPSIS ✨

struct ssam_device_uid {
    u8 domain;
    u8 category;
    u8 target;
    u8 instance;
    u8 function;
 };

🫶 Members 🫶

• domain — Domain of the device. literally the domain, bestie 🌈
• category — Target category of the device. yup, the target category 🎀
• target — Target ID of the device. the target ID, iconic 👑
• instance — Instance ID of the device. the instance ID fr fr 🍓
• function — Sub-function of the device. okay so this field can be used to split a single SAM device into multiple virtual subdevices to separate different functionality of that device and allow one driver per such functionality. that's the whole point, iykyk 💜

🔥 SEE ALSO 🔥

Kernel file ./include/linux/surface_aggregator/device.h — plus these absolute legends:

• enum ssam_device_domain(9)
• enum ssam_virtual_tc(9)
• SSAM_DEVICE(9)
• SSAM_VDEV(9)
• SSAM_SDEV(9)
• struct ssam_device(9)
• struct ssam_device_driver(9)
• is_ssam_device(9)
• to_ssam_device(9)
• to_ssam_device_driver(9)
• ssam_device_mark_hot_removed(9)
• ssam_device_is_hot_removed(9)
• ssam_device_get(9)
• ssam_device_put(9)
• ssam_device_get_drvdata(9)
• ssam_device_set_drvdata(9)
• ssam_device_driver_register(9)
• module_ssam_device_driver(9)
• ssam_register_clients(9)
• ssam_device_register_clients(9)
• SSAM_DEFINE_SYNC_REQUEST_CL_N(9)
• SSAM_DEFINE_SYNC_REQUEST_CL_W(9)
• SSAM_DEFINE_SYNC_REQUEST_CL_R(9)
• SSAM_DEFINE_SYNC_REQUEST_CL_WR(9)
• ssam_device_notifier_register(9)
• ssam_device_notifier_unregister(9)

okay that's the whole page, bestie 🫶 the source/version line is ./include/linux/surface_aggreg..., the date is October 2026, and the footer title is struct ssam_device_uid(9). mwah 💋✨