ssam_request...sync_onstack(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, you're in the Kernel API Manual, and this page is ssam_request...sync_onstack(9). The actual star of the show is ssam_request_do_sync_onstack β€” Execute a synchronous request on the stack. Slay. πŸ’…


✨ SYNOPSIS ✨

ssam_request_do_sync_onstack (ctrl , rqst , rsp , payload_len );

πŸŽ€ ARGUMENTS πŸŽ€

  • ctrl β€” the controller that the request gets submitted through.
  • rqst β€” the request specification.
  • rsp β€” the response buffer.
  • payload_len β€” the (maximum) request payload length.

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the vibe: this helper allocates a synchronous request with the specified payload length on the stack, fully initializes it via the provided request specification, submits it, and then finally waits for its completion before returning its status. Main character energy fr fr.

Essentially, this helper macro allocates the request message buffer on the stack and then calls ssam_request_do_sync_with_buffer. That's the whole glow-up. ✨


πŸ’€ NOTE πŸ’€

The payload_len parameter specifies the maximum payload length, used for buffer allocation. The actual payload length may be smaller. So don't get it twisted: max length β‰  actual length, iykyk. πŸ™ˆ


πŸ‘‘ RETURN πŸ‘‘

Returns the status of the request or any failure during setup, i.e. zero on success and a negative value on failure. Periodt. πŸ’–


🌈 SEE ALSO 🌈


Cute sign-off time: brought to you by ./include/linux/surface_aggreg... Β· October 2026 Β· page ssam_request...sync_onstack(9) πŸ’…βœ¨πŸ«Ά

πŸ“¦ where this page comes from