SSAM_DEVICE(9)

💅 SSAM_DEVICE 💅

okay bestie, so this whole page is about SSAM_DEVICE, a macro from the kernel API manual (that's the 9 in SSAM_DEVICE(9), iykyk) — and its whole personality is: it initializes a &struct ssam_device_id with the parameters you hand it. that's it, that's the vibe. 🎀

---

✨ SYNOPSIS ✨

SSAM_DEVICE (d , cat , tid , iid , fun );

like, you literally just call it with five things and it does its little matchmaking thing. slay.

---

🌸 ARGUMENTS 🌸

• d — the domain of the device. where it lives, conceptually. 🏠
• cat — the target category of the device. it's giving "what kind of thing are we even talking about".
• tid — the target ID of the device. 🆔
• iid — the instance ID of the device. (there can be several, hence instances, hence iid, periodt.)
• fun — the sub-function of the device. the little extra flavor on top. 🍓

---

💖 DESCRIPTION 💖

so what it actually does: it initializes a struct ssam_device_id with the parameters you gave it. if you want the full lore on what each of those parameters means, go read struct ssam_device_uid — that's the details girlie. 📖

now here's the fun part, the part that ate: there are these special little values —

• SSAM_SSH_TID_ANY
• SSAM_SSH_IID_ANY
• SSAM_SSH_FUN_ANY

— and you can use them to say "bestie, when matching, ignore target ID / instance ID / sub-function respectively". like a wildcard but make it fashion. wildcards for the girlies who can't commit. ✨

also, this macro initializes the match_flags field based on the parameters you pass. so it's not just vibing, it's deciding things about matching. main character energy fr fr. 👑

---

🔥 NOTE 🔥

read this part, i'm serious, no cap 🙈

• d and cat must be valid u8 values. like, that's the rule.
• tid, iid, and fun must be either valid u8 values or SSAM_SSH_TID_ANY, SSAM_SSH_IID_ANY, or SSAM_SSH_FUN_ANY, respectively. one or the other, pick a lane 💀
• any other non-u8 values? not allowed. we don't do that here. 🚫

---

🦋 SEE ALSO 🦋

okay this list is long, but every single one of these is iconic in its own way, so:

• kernel file ./include/linux/surface_aggregator/device.h
• enum ssam_device_domain(9)
• enum ssam_virtual_tc(9)
• struct ssam_device_uid(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)

go read them all, i'll wait 💜

---

and that's the page!! this whole glow-up lives at ./include/linux/surface_aggreg... and it's dated October 2026, so jot that down in your notes app bestie 🫶 see you at the next manpage, mwah 💋🌸