qcom_scm_call(9)

📦 version 7.3.1, in nixpkgs unstable

💅 qcom_scm_call(9) — Kernel API Manual 🦋

okay bestie, so this is qcom_scm_call from the Kernel API Manual — the one and only 💖

🌸 NAME 🌸

qcom_scm_call — literally just "Invoke a syscall in the secure world" ✨ like, you're calling into the secure world, no big deal, very main character energy 👑

🎀 SYNOPSIS 🎀

int qcom_scm_call (struct device *dev , const struct qcom_scm_desc *desc , struct qcom_scm_res *res );

that's the whole vibe, copy it exactly bestie, don't retype it from memory 😭

🫶 ARGUMENTS 🫶

  • dev — device 💻 that's your device handle, that's it, that's the whole thing
  • desc — Descriptor structure containing arguments and return values 📝 like it literally holds the args you're passing in and the stuff coming back out
  • res — Structure containing results from SMC/HVC call 🎁 this one's where the SMC/HVC call drops off its results

⭐ DESCRIPTION ⭐

Sends a command to the SCM and waits for the command to finish processing. 🕐✨ like, you send it, and then you wait, because it's not a "fire and forget" situation, it's a "fire and then stand there watching" situation 🙈

⚠️ ok this part is serious, no cap: this should only be called in pre-emptible context. ONLY. in pre-emptible context. not negotiable, not a suggestion, not a "well maybe just this once" — pre-emptible context or nothing 🔥

💜 SEE ALSO 💜

Kernel file ./drivers/firmware/qcom/qcom_scm.c — go read the source, iykyk 📖

and the whole friend group of related functions, all of them, every single one (not me listing all of these, but we keep the facts fr fr):

and that's the page bestie, go call your secure world syscalls responsibly 🌈💅

source path ./drivers/firmware/qcom, dated October 2026 — mwah, love that for us 🍓🫶🧚

📦 where this page comes from