qcomtee_supp_recv(9)

💖 NAME 💖

qcomtee_supp_recv(9) — from the Kernel API Manual, bestie, this one literally waits for a request for the supplicant. That's the whole assignment. 💅

✨ SYNOPSIS ✨

int qcomtee_supp_recv (struct tee_context *ctx , u32 *op , u32 *num_params , struct tee_param *params );

🎀 ARGUMENTS 🎀

• ctx — TEE context. The main-character setup, basically. 💖
• op — requested operation on the object. It's giving "what are we doing today." ✨
• num_params — number of elements in the parameter array. Keep count, babe. 🧮
• params — parameters for op. The whole little squad of values. 🫶

🦋 DESCRIPTION 🦋

Okay so picture this: the first parameter is a meta TEE_IOCTL_PARAM_ATTR_TYPE_VALUE_INOUT. On input, it provides a user buffer. That buffer is used for parameters of type TEE_IOCTL_PARAM_ATTR_TYPE_UBUF_INPUT in qcomtee_cb_params_from_args. On output, the object ID and request ID are stored in the meta parameter. No cap, that's the flow. 🌈

And num_params? It is updated to the number of parameters that actually exist in params on return. Slay. ✨

🔥 RETURN 🔥

On success, returns 0; on failure, returns < 0. Periodt. 💀

🌈 SEE ALSO 🌈

• Kernel file: ./drivers/tee/qcomtee/call.c
• qcomtee_context_add_qtee_object(9)
• qcomtee_context_del_qtee_object(9)
• qcomtee_objref_to_arg(9)
• qcomtee_objref_from_arg(9)
• qcomtee_params_to_args(9)
• qcomtee_params_from_args(9)
• qcomtee_object_invoke(9)
• qcomtee_supp_send(9)
• qcomtee_get_qtee_feature_list(9)
• qcomtee_remove(9)

mwah 💋 — source/version: ./drivers/tee/qcomtee, date: October 2026. 🎀