USER OBJECTS AKA SUPPLICANTS(9)

💅 User Objects aka Supplicants 💅

Kernel API Manual · manual name: Supplicants(9) · okay so bestie, we are literally in the kernel docs and the vibes are immaculate ✨

The whole concept, no cap: any userspace process with access to the TEE device file can behave as a supplicant by creating a user object. And any TEE parameter of type OBJREF with the QCOMTEE_OBJREF_FLAG_USER flag set is considered a user object. That's the rule, periodt. 💅

A supplicant uses qcomtee_user_object_select (i.e. TEE_IOC_SUPPL_RECV) to receive a QTEE user object request, and qcomtee_user_object_submit (i.e. TEE_IOC_SUPPL_SEND) to submit a response. 🫶 QTEE expects to receive the response, including OB and OO, in a specific order in the message; parameters submitted with qcomtee_user_object_submit should maintain this order. Do not mess with that order, bestie — it's giving important 😭

🔎 SEE ALSO 🔎

• Kernel file ./drivers/tee/qcomtee/user_obj.c struct
• qcomtee_user_object(9)
• enum qcomtee_req_state(9)
• ureq_dequeue(9)
• ureq_select(9)
• qcomtee_user_param_to_object(9)
• qcomtee_cb_params_from_args(9)
• qcomtee_cb_params_to_args(9)
• qcomtee_user_object_select(9)
• qcomtee_user_object_submit(9)

And that's a wrap, bestie 💖 source/version: ./drivers/tee/qcomtee · date: October 2026 · manual label: User Objects... Supplicants(9) — slay, go read that kernel file 🎀