qcom_scm_qt...ack_response(9)

💖 NAME 💖

Okay bestie, this page is qcom_scm_qt...ack_response(9) from the Kernel API Manual, and the function is literally qcom_scm_qtee_callback_response — Submit response for callback request. 💅

---

✨ SYNOPSIS ✨

int qcom_scm_qtee_callback_response (phys_addr_t buf , size_t buf_size ,
       u64 *result , u64 *response_type );

---

🎀 ARGUMENTS 🎀

• buf — start address of memory area used for outbound buffer. 📍
• buf_size — size of the memory area used for outbound buffer. 📏
• result — Result of QTEE object invocation. 🧾
• response_type — Response type returned by QTEE. 🏷️

---

🦋 DESCRIPTION 🦋

So like, response_type is the main character here: it determines how the contents of buf should be processed. That's the vibe check. ✨

---

🌸 RETURN 🌸

On success, return 0 or <0 on failure. That's it, that's the whole energy. 💖

---

👑 SEE ALSO 👑

Kernel file ./drivers/firmware/qcom/qcom_scm.c struct qcom_scm_qseecom_resp(9) — plus the whole squad, no cap:

• qcom_scm_call(9)
• qcom_scm_call_atomic(9)
• qcom_scm_set_warm_boot_addr(9)
• qcom_scm_set_cold_boot_addr(9)
• qcom_scm_cpu_power_down(9)
• qcom_scm_is_pas_available(9)
• qcom_scm_restore_sec_cfg_available(9)
• qcom_scm_assign_mem(9)
• qcom_scm_ocmem_lock_available(9)
• qcom_scm_ocmem_lock(9)
• qcom_scm_ocmem_unlock(9)
• qcom_scm_ice_available(9)
• qcom_scm_ice_invalidate_key(9)
• qcom_scm_ice_set_key(9)
• qcom_scm_derive_sw_secret(9)
• qcom_scm_generate_ice_key(9)
• qcom_scm_prepare_ice_key(9)
• qcom_scm_import_ice_key(9)
• qcom_scm_hdcp_available(9)
• qcom_scm_hdcp_req(9)
• qcom_scm_qseecom_call(9)
• qcom_scm_qseecom_get_version(9)
• qcom_scm_qseecom_app_get_id(9)
• qcom_scm_qseecom_app_send(9)
• qcom_scm_qtee_invoke_smc(9)
• qcom_scm_is_available(9)

---

Made with 🫶 from ./drivers/firmware/qcom, dated October 2026, and this has been your qcom_scm_qt...ack_response(9) moment — bye bestie! 🎀🦋💜