STRUCT QCOMTEE_CONTEXT_DATA(9)

okay bestie, welcome to the Kernel API Manual glow-up for struct qcomtee_context_data(9) 🫶 this page is literally about the context for clients or supplicants, and we are gonna cover every single field, no cap.

✨ NAME ✨

struct qcomtee_context_data — clients' or supplicants' context. 💖

🎀 SYNOPSIS 🎀

here's the whole struct, copied exactly because we do not mess with code, periodt:

       struct qcomtee_context_data {
           struct idr qtee_objects_idr;
           struct mutex qtee_lock;
           struct idr reqs_idr;
           struct list_head reqs_list;
           struct mutex reqs_lock;
           struct completion req_c;
           bool released;
        };

💅 Members 💅

okay so this struct is giving little container-of-everything energy, and each member has its own job:

• qtee_objects_idr — QTEE objects in this context. 👑
• qtee_lock — mutex for qtee_objects_idr. 🔒
• reqs_idr — requests in this context that hold ID. 🪪
• reqs_list — FIFO for requests in PROCESSING or QUEUED state. 🌀
• reqs_lock — mutex for reqs_idr, reqs_list and request states. 🔐
• req_c — completion used when the supplicant is waiting for requests. ⏳
• released — state of this context. 🦋

🌈 SEE ALSO 🌈

go peek at these besties, iykyk:

• Kernel file ./drivers/tee/qcomtee/qcomtee.h
• struct qcomtee(9)
• qcomtee_object_do_invoke_internal(9)
• struct qcomtee_user_object_request_data(9)
• qcomtee_memobj_param_to_object(9)
• qcomtee_mem_object_map(9)

and that's the whole vibe check 💖 this iconic page comes from source/version ./drivers/tee/qcomtee, dated October 2026, and it's forever the struct qcomtee_context_data(9) manual-page main character. bye bestie, go read those SEE ALSOs 🌸✨