qcomtee_user_object_select(9)

💅 qcomtee_user_object_select — the kernel manual, but make it make sense

okay so bestie, this page lives in the Kernel API Manual and it's all about qcomtee_user_object_select — the function that selects a request for a user object. yes, that's the whole vibe. let's get into it 🎀

---

✨ SYNOPSIS ✨

int qcomtee_user_object_select (struct tee_context *ctx , struct
       tee_param *params , int num_params , void __user *uaddr , size_t size ,
       struct qcomtee_user_object_request_data *data );

that's the whole signature, no cap — six args, one int return, and it's giving very "I do one thing and I do it well" 💅

---

🌸 ARGUMENTS 🌸

so here's the cast of characters, one by one, no skips:

• ctx — the context where we go looking for a user object. like, this is the neighborhood we're searching in 🏘️
• params — the parameters for the op. the actual op, bestie.
• num_params — how many elements are in that parameter array. gotta know how many you're working with 🔢
• uaddr — the user buffer for the output UBUF parameters. that's where the output goes 💌
• size — the size of the user buffer uaddr. because we don't just yeet into a buffer of unknown size fr fr
• data — the info for the selected request. like the little profile card for whichever request got picked 👑

---

🦋 DESCRIPTION 🦋

okay so here's the whole deal: params gets filled in, along with data, for the request that was selected. that's it. that's the sentence. short and iconic, honestly ✨

it's giving "one line of prose but it's doing exactly what it needs to do" 💜

---

🌈 RETURN 🌈

• on success → returns 0 ✅ slay
• on failure → returns < 0 😭 not slay

that's it. no ambiguity. a true legend.

---

👑 SEE ALSO 👑

go read these next, bestie, they're all connected and honestly they ate:

• Kernel file ./drivers/tee/qcomtee/user_obj.c
• User Objects aka Supplicants(9)
• 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_submit(9)

like, read them in that order or don't, I'm not your mom, but they're all the same little friend group 🫶

---

⭐ real talk: this is kernel API territory, so keep the args exactly as typed — ctx, params, num_params, uaddr, size, data — and don't go freelancing with the types. iykyk 💀

---

and that's the page!! mwah 💖 this one came from ./drivers/tee/qcomtee, dated October 2026 — soak it in, it's literally a whole vibe check for a kernel interface 🌸💅