qcom_qseecom_app_send(9)

💅 qcom_qseecom_app_send(9) — the Kernel API Manual moment

okay so bestie, welcome to the Kernel API Manual page for qcom_qseecom_app_send, and yes we're doing this properly 💖

✨ NAME ✨

qcom_qseecom_app_send — send stuff to a QSEE app and get data back from it. That's the whole vibe.

✨ SYNOPSIS ✨

int qcom_qseecom_app_send (struct qseecom_client *client , void *req ,
       size_t req_size , void *rsp , size_t rsp_size );

look at that signature. gorgeous. no notes 🎀

✨ ARGUMENTS ✨

• client — the QSEECOM client that's tied to whichever app you're targeting. this is your main character pointer 💅
• req — the request buffer you're sending over to the app. must be TZ memory, no exceptions, i don't make the rules (the kernel does).
• req_size — size of the request buffer. literally just how big req is ✨
• rsp — the response buffer, and the app writes into it. also must be TZ memory 🫶
• rsp_size — size of the response buffer. how much room the app has to write back 💖

✨ DESCRIPTION ✨

so what this does is: it sends a request to the QSEE app that your client is associated with, and then reads the response back out. that's it, that's the whole thing 🌸

the caller has to supply two DMA memory regions — one for the request, one for the response — and fill out the req region with the request data (which is app-specific, so like, whatever that particular app expects, iykyk). then the QSEE app reads it and returns its response in the rsp region. iconic behaviour honestly 🦋

✨ NOTE ✨

this is a convenience wrapper around qcom_scm_qseecom_app_send. and like — clients should prefer to use this wrapper. it's the nicer one. use the nice one 💜

✨ RETURN ✨

• Zero on success ✨
• nonzero on failure 😭

✨ SEE ALSO ✨

• Kernel file ./include/linux/firmware/qcom/qcom_qseecom.h
• struct qseecom_client(9)

---

and that's the page, bestie 🎀 real ones know this came from the ./include/linux/firmware/qcom of it all, October 2026, qcom_qseecom_app_send(9) — periodt 💅✨