qcom_scm_qtee_invoke_smc(9)

📦 version 7.3.1, in nixpkgs unstable

okay bestie, welcome to qcom_scm_qtee_invoke_smc(9) from the Kernel API Manual — yes, the QTEE object invocation page — and we're gonna make it make sense 💅✨

🎀 NAME 🎀

qcom_scm_qtee_invoke_smc — Invoke a QTEE object. That's the name, that's the mission, periodt 👑

✨ SYNOPSIS ✨

int qcom_scm_qtee_invoke_smc (phys_addr_t inbuf , size_t inbuf_size ,
       phys_addr_t outbuf , size_t outbuf_size , u64 *result , u64
       *response_type );

🦋 ARGUMENTS 🦋

  • inbuf — start address of the memory area used for the inbound buffer. literally where the inbound buffer begins 💖
  • inbuf_size — size of the memory area used for the inbound buffer.
  • outbuf — start address of the memory area used for the outbound buffer.
  • outbuf_size — size of the memory area used for the outbound buffer.
  • result — result of the QTEE object invocation.
  • response_type — response type returned by QTEE.

🌸 DESCRIPTION 🌸

okay so here's the lowkey important bit: response_type determines how the contents of inbuf and outbuf should be processed. that's the whole rule, no cap ✨

🔥 RETURN 🔥

On success, return 0 or <0 on failure.

💜 SEE ALSO 💜

the whole linked bestie list, right here 🫶:

okay that's the page!! source/version vibes: ./drivers/firmware/qcom · qcom_scm_qtee_invoke_smc(9) · date: October 2026 — byeee 💖🫶

📦 where this page comes from