qcom_scm_ocmem_lock(9)
β¨ qcom_scm_ocmem_lock(9) β¨
okay so bestie, this page is from the Kernel API Manual, and the main character is qcom_scm_ocmem_lock(9). it's giving firmware-girl realness: this is the call to the OCMEM lock interface that assigns an OCMEM region to the initiator you specify. no cap. π¦
π NAME π
qcom_scm_ocmem_lock β call OCMEM lock interface to assign an OCMEM region to the specified initiator.
πΈ SYNOPSIS πΈ
int qcom_scm_ocmem_lock (enum qcom_scm_ocmem_client id , u32 offset ,
u32 size , u32 mode );
π ARGUMENTS π
idβ tz initiator id. this is the initiator ID from tz, periodt.offsetβ OCMEM offset. literally the offset into OCMEM.sizeβ OCMEM size. how much OCMEM we're talking about.modeβ access mode (WIDE/NARROW). pick your mode, bestie.
π¦ SEE ALSO π¦
the kernel file is ./drivers/firmware/qcom/qcom_scm.c, and here's the whole squad of related references β yes, all of them, we're not skipping anybody:
struct qcom_scm_qseecom_resp(9)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_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_qtee_callback_response(9)qcom_scm_is_available(9)
xoxo, your local Unix bestie π
β page source/version: ./drivers/firmware/qcom; date: October 2026; page: qcom_scm_ocmem_lock(9). π«Ά
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms