optee_supp_recv(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– optee_supp_recv(9) β€” Kernel API Manual πŸ’–

okay so bestie, welcome to the optee_supp_recv page β€” this is the 9 section of the Kernel API Manual, and we're literally about to make supplicant request-receiving make sense. periodt. ✨


🌸 NAME 🌸

optee_supp_recv β€” receive request for supplicant 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

int optee_supp_recv (struct tee_context *ctx , u32 *func , u32
       *num_params , struct tee_param *param );

that's the whole vibe. one function, four args, no cap. πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • ctx β€” the context that's receiving the request. like, whose inbox is this landing in. πŸ“₯
  • func β€” the requested function in the supplicant. the "what do they want from me" energy. ✨
  • num_params β€” the number of elements allocated in param, and it gets updated with the number of used elements. yes bestie, it's an in-and-out situation β€” it comes in as the count and leaves telling you how many actually got used. πŸ”„
  • param β€” the space for parameters for func. this is where the actual deets live. 🧚

⭐ DESCRIPTION ⭐

returns 0 on success or <0 on failure. that's it, that's the whole story β€” check the return value, always, i'm begging. 😭


🌈 SEE ALSO 🌈

kernel file ./drivers/tee/optee/supp.c, plus the sibling icons:

go read those too, iykyk. πŸ‘‘


and that's a wrap, bestie πŸŽ€ this little beauty lives in ./drivers/tee/optee and it's dated October 2026 β€” mwah, slay, bye πŸ’…πŸ’–

πŸ“¦ where this page comes from