qcom_scm_qseecom_app_send(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

qcom_scm_qseecom_app_send — bestie, this is the <rainbow>"send stuff to a QSEE app and get stuff back"</rainbow> function 🫶 straight out of the Kernel API Manual ✨

🌸 SYNOPSIS 🌸

int qcom_scm_qseecom_app_send (u32 app_id , void *req , size_t req_size
, void *rsp , size_t rsp_size );

No cap, that's the whole vibe 💅

🎀 ARGUMENTS 🎀

  • app_id — the ID of the target app 🎯 like, which QSEE app you're sliding into.
  • req — the request buffer you send over to the app. Heads up: must be TZ memory ⚠️
  • req_size — size of the request buffer 📏
  • rsp — the response buffer, and the app writes into this one. Also must be TZ memory ⚠️
  • rsp_size — size of the response buffer 📏

🦋 DESCRIPTION 🦋

okay so here's the tea ☕ this function sends a request to the QSEE app that's associated with the given ID, then reads back that app's response. Simple as that ✨

But — and this is the part you cannot skip, bestie — the caller must provide two DMA memory regions, one for the request and one for the response 😭

Then you fill out the req region with the respective (app-specific) request data 💌 The QSEE app reads that, and hands you back its response in the rsp region. it's giving pen pal energy, honestly 🍓

🔥 reminder: req and rsp must both be TZ memory. Don't come crying to me if you forget 😤

👑 RETURN 👑

  • Zero on success 🎉 slay
  • Nonzero on failure 💀 sad but that's the game

🌈 SEE ALSO 🌈

Kernel file ./drivers/firmware/qcom/qcom_scm.c struct qcom_scm_qseecom_resp(9), plus the whole friend group 😌:

and that's the whole page, bestie 🧚💜 this one lives over in ./drivers/firmware/qcom, dated October 2026 — mwah, go ship something iconic 💅✨🎀

📦 where this page comes from