qcom_scm_ocmem_unlock(9)

📦 version 7.3.1, in nixpkgs unstable

💅 qcom_scm_ocmem_unlock — bestie's guide to the kernel API manual

okay so picture this: we're deep in the Linux kernel docs, right in qcom_scm_ocmem_unlock(9), and honestly? this one's a little legend. Let me put you on. 🫶

✨ NAME ✨

qcom_scm_ocmem_unlock — literally just calls the OCMEM unlock interface so an OCMEM region gets released from the initiator you point at. That's the whole vibe. No cap. 🦋

🌸 SYNOPSIS 🌸

int qcom_scm_ocmem_unlock (enum qcom_scm_ocmem_client id , u32 offset ,
       u32 size );

like, that's it. three lil arguments and it returns an int. the way that it's so short and yet so iconic 😭

🎀 ARGUMENTS 🎀

  • id — the tz initiator id 💫 (yes, that's the one that has to match up with your enum qcom_scm_ocmem_client, no notes)
  • offset — the OCMEM offset, as promised 📍
  • size — and the OCMEM size. slay. that's the region, bestie 💖
ngl, each one of these is doing exactly what the label says — no secret lore here, just id, offset, size. lowkey refreshing.

🦋 SEE ALSO 🦋

okay this list is long and every single entry stays, because we don't do skipping around here 👑

Kernel file ./drivers/firmware/qcom/qcom_scm.c struct, plus:

main character energy across the whole SCM family, fr fr 🌈

it's giving "small function, huge ecosystem." go read the neighbors if you want the full story 💀

✨ okay that's the page!! sign-off time: this lil beauty lives in ./drivers/firmware/qcom and the version stamp is from October 2026 — so like, technically future-dated, which is very main character of it. mwah 💋🎀

📦 where this page comes from