ssam_device_alloc(9)

💅 ssam_device_alloc — from the Kernel API Manual (section 9), bestie ✨

okay so picture this: you're deep in the kernel, you need a shiny new SSAM client device, and this is the function that hands it to you. no cap.

---

✨ SYNOPSIS ✨

struct ssam_device * ssam_device_alloc (struct ssam_controller *ctrl ,
struct ssam_device_uid uid );

like, two args, one pointer out. simple. iconic. 🎀

---

🌸 ARGUMENTS 🌸

• ctrl — the controller that this device is gonna live under. that's its whole home situation 🏠
• uid — the UID of the device you're adding. it's literally the device's name tag 🫶

---

💖 DESCRIPTION 💖

so what it does is allocate and initialize a brand-new client device. fresh out the box, bestie ✨

The parent of the device gets set to the controller device, and the name gets set based on the UID. cute, right?

⚠️ but listen — the device still has to be added via ssam_device_add. allocating it is not the same as adding it. you gotta go read that function for the deets, fr fr. don't skip it 🙈

---

👑 RETURN 👑

Returns the newly allocated and initialized SSAM client device 💅 or, if it could not be allocated, NULL. yeah. sad girl hours 😭 always check for the NULL, okay?

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/platform/surface/aggregator/bus.c

• ssam_device_add(9)
• ssam_device_remove(9)
• ssam_device_id_compatible(9)
• ssam_device_id_is_null(9)
• ssam_device_id_match(9)
• ssam_device_get_match(9)
• ssam_device_get_match_data(9)
• __ssam_device_driver_register(9)
• ssam_device_driver_unregister(9)
• ssam_bus_register(9)
• ssam_bus_unregister(9)
• __ssam_register_clients(9)
• ssam_remove_clients(9)

that's the whole friend group, they all hang out together 🦋

---

and that's the page!! mwah 💋 this one came from ./drivers/platform/surface/agg... and it's dated October 2026 — so like, future slay ⭐ go forth and allocate responsibly, bestie 🧚💜