SSAM_DEFINE...REQUEST_MD_W(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay so bestie, welcome to the SSAM_DEFINE...REQUEST_MD_W(9) page from the Kernel API Manual πŸ’… β€” this one is all about SSAM_DEFINE_SYNC_REQUEST_MD_W, which defines a synchronous multi-device SAM request function with an argument. no cap.

πŸŽ€ SYNOPSIS πŸŽ€

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

πŸ¦‹ ARGUMENTS πŸ¦‹

  • name β€” the name of the generated function, periodt.
  • atype β€” the type of the request’s argument.
  • spec β€” the specification (struct ssam_request_spec_md) that defines the request. this is the blueprint, okay?

πŸ’– DESCRIPTION πŸ’–

So this macro defines a function that executes the synchronous SAM request specified by spec. The request takes an argument of type atype and has no return value. The device-specifying parameters are not hard-coded β€” instead they must be provided to the function. The generated function takes care of setting up the request struct, buffer allocation, as well as execution of the request itself, returning once the request has been fully completed. The required transport buffer will be allocated on the stack. slay.

The generated function is defined as:

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

It returns the status of the request: zero on success and negative on failure. The ctrl parameter is the controller via which the request is sent, tid is the target ID for the request, and iid is the instance ID. The request argument is specified via the arg pointer. iykyk.

For more details on the behavior of the generated function, refer to ssam_request_do_sync_onstack. πŸ’«

🌈 SEE ALSO 🌈

Kernel file ./include/linux/surface_aggregator/controller.h, plus these iconic references:


mwah πŸ’‹ this page is from ./include/linux/surface_aggreg..., dated October 2026, and the manual name is SSAM_DEFINE...REQUEST_MD_W(9) β€” bye bestie 🫢✨

πŸ“¦ where this page comes from