qcomtee_get_async_buffer(9)

💜 qcomtee_get_async_buffer(9) 💜

okay bestie, welcome to the kernel API manual for qcomtee_get_async_buffer — section 9, the deep magic zone ✨

---

🌸 NAME 🌸

qcomtee_get_async_buffer — literally just get the start of the asynchronous message. that's the whole vibe 🫶

---

✨ SYNOPSIS ✨

void qcomtee_get_async_buffer (struct qcomtee_object_invoke_ctx *oic ,
struct qcomtee_buffer *async_buffer );

---

🎀 ARGUMENTS 🎀

• oic — the context used for the current invocation. it's giving "the situation we're currently in" energy 💅
• async_buffer — the return buffer you extract from or fill in async messages with. bestie this is where the data goes 🦋

---

🔥 DESCRIPTION 🔥

okay so here's the tea ☕ — what you actually get back depends on how oic is being used:

• if oic is used for a direct object invocation, then the whole outbound buffer is available for the async message. the entire thing. no cap, all yours 👑
• if oic is used for a callback request, then it's just the tail of the outbound buffer — the part that comes after the callback request message — that's available for the async message. scraps only, but cute scraps 💀

and the start of the async buffer is aligned, see qcomtee_msg_offset_align. alignment matters, don't @ me 🧚

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/tee/qcomtee/async.c struct
• qcomtee_async_msg_hdr(9)
• struct qcomtee_async_release_msg(9)
• async_release(9)
• qcomtee_fetch_async_reqs(9)

go read those too, iykyk ⭐

---

💖 lowkey reminder: this page lives in ./drivers/tee/qcomtee, dated October 2026, and it's page qcomtee_get_async_buffer(9) of the Kernel API Manual. slay, you're all caught up — periodt 🎀💅