SSAM_DEFINE_SYNC_REQUEST_W(9)

💅 SSAM_DEFINE_SYNC_REQUEST_W(9) — like, the Kernel API Manual page, bestie ✨

okay so picture this: you're deep in the Kernel API Manual (yes, that one, the SSAM_DEFINE_SYNC_REQUEST_W(9) page, section 9, we love a numbered section) and you need a synchronous SAM request function that takes an argument. Say less. This macro has you covered, and honestly? It ate. 🫶

---

✨ NAME ✨

SSAM_DEFINE_SYNC_REQUEST_W — define a synchronous SAM request function with an argument. That's the whole vibe. No return value, one argument, done. 🎀

---

🌸 SYNOPSIS 🌸

SSAM_DEFINE_SYNC_REQUEST_W (name , atype , spec... );

(yes, the spacing is exactly like that, don't come for me, I'm just the messenger 💀)

---

🦋 ARGUMENTS 🦋

• name — the name of the function you're generating. You get to pick it! Main character energy, truly. 👑
• atype — the type of the request's argument. So like, what kind of thing are we passing in here.
• spec — the specification (that's a struct ssam_request_spec) that defines the request. This is the blueprint, the mood board, the whole plan. ✨

---

💖 DESCRIPTION 💖

Okay so what this macro actually does: it defines a function that executes the synchronous SAM request specified by spec, where the request takes an argument of type atype and has no return value. Like, none. Zero. Nada. 💀

The generated function is literally doing the most for you — it sets up the request struct, it handles buffer allocation, and it executes the request itself, returning once the request has been fully completed. And the required transport buffer? Allocated on the stack. We love a low-effort allocation moment. 🌈

The generated function is defined as:

static int name(struct ssam_controller *ctrl, const atype *arg)

and it returns the status of the request: zero on success, negative on failure. Periodt. 💅

So the ctrl parameter is the controller via which the request is sent (the messenger 🧚), and the request argument is specified via the arg pointer (the actual payload, the star of the show ⭐).

If you wanna know more about how the generated function behaves — like, the full lore — go check out ssam_request_do_sync_onstack. It's giving "read the docs" but make it cute. 🙈

---

🔥 SEE ALSO 🔥

Kernel file ./include/linux/surface_aggregator/controller.h, plus the whole friend group:

• enum ssam_event_flags(9)
• struct ssam_event(9)
• enum ssam_request_flags(9)
• struct ssam_request(9)
• struct ssam_response(9)
• struct ssam_request_sync(9)
• ssam_request_sync_set_data(9)
• ssam_request_sync_set_resp(9)
• ssam_request_sync_wait(9)
• ssam_request_do_sync_onstack(9)
• __ssam_retry(9)
• ssam_retry(9)
• struct ssam_request_spec(9)
• struct ssam_request_spec_md(9)
• SSAM_DEFINE_SYNC_REQUEST_N(9)
• SSAM_DEFINE_SYNC_REQUEST_R(9)
• SSAM_DEFINE_SYNC_REQUEST_WR(9)
• SSAM_DEFINE_SYNC_REQUEST_MD_N(9)
• SSAM_DEFINE_SYNC_REQUEST_MD_W(9)
• SSAM_DEFINE_SYNC_REQUEST_MD_R(9)
• SSAM_DEFINE_SYNC_REQUEST_MD_WR(9)
• enum ssam_notif_flags(9)
• struct ssam_notifier_block(9)
• ssam_notifier_from_errno(9)
• ssam_notifier_to_errno(9)
• struct ssam_event_registry(9)
• struct ssam_event_id(9)
• enum ssam_event_mask(9)
• SSAM_EVENT_REGISTRY(9)
• enum ssam_event_notifier_flags(9)
• struct ssam_event_notifier(9)
• ssam_notifier_unregister(9)

---

ngl bestie, this whole page lives at ./include/linux/surface_aggreg... and it's dated October 2026, so go off, time traveler 🕰️✨

and that's the page!! sourced from the Kernel API Manual, dated October 2026, file ./include/linux/surface_aggreg... — mwah, ty for reading, ily, bye 💜🎀🦋