gb_operation_sync_timeout(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– gb_operation_sync_timeout(9) πŸ’–

okay so bestie, you're in the Kernel API Manual (section 9, keep up ✨) and we're about to talk about gb_operation_sync_timeout β€” literally the "just send it and wait" of Greybus. no cap. πŸ¦‹


✨ NAME ✨

gb_operation_sync_timeout β€” implement a "simple" synchronous operation πŸŽ€


🌸 SYNOPSIS 🌸

int gb_operation_sync_timeout (struct gb_connection *connection , int
type , void *request , int request_size , void *response , int
response_size , unsigned int timeout );

🧚 ARGUMENTS 🧚

  • connection β€” the Greybus connection we're sending this whole thing to, like it's the group chat you're dropping the message in πŸ’…
  • type β€” the type of operation you're sending, iykyk
  • request β€” pointer to a memory buffer; we copy the request from here 🫢
  • request_size β€” size of request, obviously
  • response β€” pointer to a memory buffer; we copy the response to here
  • response_size β€” the size of response. periodt.
  • timeout β€” operation timeout in milliseconds ⏳

πŸ”₯ DESCRIPTION πŸ”₯

This function implements a simple synchronous Greybus operation. like, simple simple. it sends the provided operation request and then waits (yes, sleeps 😴) until the corresponding operation response message has been successfully received, or until an error occurs. whichever comes first, bestie.

request and response are buffers holding the request and response data respectively, and if they are not NULL, their size must be specified in request_size and response_size. no guessing, just say the number πŸ’€

If a response payload is to come back, and response is not NULL, then response_size number of bytes will be copied into response β€” but only if the operation is successful ✨

If there is an error, the response buffer is left alone. completely untouched. hands off. πŸ™ˆ

fr fr, that last bit matters β€” on error your buffer does not get written to, so don't go reading it like it's fresh data πŸ‘‘

⭐ SEE ALSO ⭐

Kernel file ./drivers/greybus/operation.c, gb_operation_request_send(9), gb_operation_unidirectional_timeout(9) 🌈


and that's the whole vibe check, bestie πŸ’œ this page came to you from ./drivers/greybus, dated October 2026, and the title is gb_operation_sync_timeout(9) β€” slay, go write some kernel code now πŸ’…πŸŽ€

πŸ“¦ where this page comes from