qcom_scm_oc...ck_available(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

qcom_scm_ocmem_lock_available β€” bestie, this is literally the vibe check for whether the OCMEM lock/unlock interface is even available πŸ’…

(oh also hiii, you're reading a page from the Kernel API Manual, section 9 β€” welcome to the group chat 🫢)


✨ SYNOPSIS ✨

bool qcom_scm_ocmem_lock_available (void );

ok so it's a bool, it takes nothing, and it just tells you yes or no. iconic honestly πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • void β€” no arguments. not a single one. zero. nada. it needs absolutely nothing from you, which honestly? main character behaviour. it just shows up, answers the question, and leaves πŸ’β€β™€οΈ

πŸ¦‹ SEE ALSO πŸ¦‹

the whole friend group, no cap β€” these all hang out together:

🧚 and if you wanna go to the source (literally), the kernel file is ./drivers/firmware/qcom/qcom_scm.c β€” that's where struct qcom_scm_qseecom_resp(9) and all the rest actually live. iykyk 😌

that's the whole page, bestie β€” short, sweet, and highkey perfect πŸ“

πŸ’– brought to you by ./drivers/firmware/qcom πŸ’– πŸ—“οΈ October 2026 πŸ—“οΈ πŸ‘‘ Kernel API Manual, section 9 πŸ‘‘

mwah, go forth and check those availability flags, periodt πŸ’œ

πŸ“¦ where this page comes from