wkup_m3_set_mem_type(9)
π NAME π
okay so bestie, welcome to wkup_m3_set_mem_type(9) β the Kernel API Manual page for wkup_m3_set_mem_type, which passes wkup_m3 which type of memory is in use. that's the whole name-line vibe, and honestly it's giving βsmall function, big suspend/resume responsibilities.β β¨
π SYNOPSIS π
void wkup_m3_set_mem_type (struct wkup_m3_ipc *m3_ipc , int mem_type );
πΈ ARGUMENTS πΈ
m3_ipcβ pointer to thewkup_m3_ipccontext. like, the context bestie, the wholewkup_m3_ipcsituation. π«Άmem_typeβ memory type value read directly fromemif. no cap, it comes straight fromemif. π
π¦ DESCRIPTION π¦
wkup_m3 must know what memory type is in use so it can properly suspend and resume. like, that is literally non-negotiable β suspend and resume need the memory-type tea, and this function is the one passing it along. πβ¨
π₯ SEE ALSO π₯
- Kernel file
./drivers/soc/ti/wkup_m3_ipc.c wkup_m3_copy_aux_data(9)wkup_m3_set_resume_address(9)wkup_m3_request_pm_status(9)wkup_m3_prepare_low_power(9)wkup_m3_finish_low_power(9)wkup_m3_request_wake_src(9)wkup_m3_set_rtc_only(9)wkup_m3_ipc_get(9)wkup_m3_ipc_put(9)
mwah π this iconic little page is brought to you by source/version ./drivers/soc/ti, dated October 2026, and it's literally wkup_m3_set_mem_type(9). periodt. π
π¦ 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