STRUCT QCOMTEE_MSG_OBJECT_INVOKE(9)

💖 NAME 💖

okay bestie, you're looking at the manual page for struct qcomtee_msg_object_invoke in the Kernel API Manual, section 9. it is literally the Direct object invocation message and that's the whole vibe. periodt. 💅

✨ SYNOPSIS ✨

       struct qcomtee_msg_object_invoke {
           u32 cxt;
           u32 op;
           u32 counts;
           union qcomtee_msg_arg args[];
        };

🫶 Members 🫶

• cxt — object ID hosted in QTEE. no cap.
• op — operation for the object. yes bestie.
• counts — number of different types of arguments in args. it's counting the arg types.
• args — array of arguments. literally the arg pile.

💅 Description 💅

okay so counts consists of 4 * 4-bit fields. Let's break the bits down, because this part is lowkey iconic:

• Bits 0 - 3 represent the number of input buffers.
• Bits 4 - 7 represent the number of output buffers.
• Bits 8 - 11 represent the number of input objects.
• Bits 12 - 15 represent the number of output objects.

The remaining bits should be zero. 🫶

here's the cute little diagram, bestie:

       15            12 11             8 7              4 3              0

       ┌───────────────────────────────────────────────────────────┐
       │     #OO objects   #IO objects   #OB buffers   #IB buffers │
       └───────────────────────────────────────────────────────────┘

The maximum number of arguments of each type is defined by QCOMTEE_ARGS_PER_TYPE.

🌈 SEE ALSO 🌈

go read these too, bestie:

• Kernel file ./drivers/tee/qcomtee/qcomtee_msg.h ''Qualcomm TEE'' (QTEE) Transport Message(9)
• QCOMTEE_MSG_OBJECT_NS_BIT(9)
• struct qcomtee_msg_callback(9)

that's the whole page, bestie 💖 — source/version: ./drivers/tee/qcomtee, date: October 2026. byeee ✨🦋