meson_sm_call(9)
π meson_sm_call(9) β welcome to the Kernel API Manual, bestie π
Okay so picture this: you're in the Kernel API Manual and there's exactly one function you need to make the secure-monitor do your bidding. That's this one. It's a generic SMC32 call. Lowkey iconic, highkey essential. Let's go π«Ά
β¨ NAME β¨
meson_sm_call β the generic SMC32 call to the secure-monitor. That's it, that's the whole vibe π
πΈ SYNOPSIS πΈ
int meson_sm_call (struct meson_sm_firmware *fw , unsigned int cmd_index
, s32 *ret , u32 arg0 , u32 arg1 , u32 arg2 , u32 arg3 , u32 arg4 );
Yes bestie, that's a lot of arguments. Eight whole parameters. She's got range π
π¦ ARGUMENTS π¦
fwβ pointer to the secure-monitor firmware. This is your main character, the root of everything πcmd_indexβ index of the SMC32 function ID. Basically which thing you're asking the secure-monitor to do β¨retβ the returned value. She holds the answer and she's not subtle about it πarg0β SMC32 Argument 0. First one, obviously π«arg1β SMC32 Argument 1. Second, keeping the streak alive πarg2β SMC32 Argument 2. She's here, she's numbered πarg3β SMC32 Argument 3. Almost at the end, hang on πarg4β SMC32 Argument 4. The finale!! The last one!! π
ngl, that's a whole roster of args, but each one has a job and they're all doing it. Respect fr fr π
π₯ RETURN π₯
0 on success β slay, everything worked π
A negative value on error β not the vibe, but at least you know something went sideways π
π SEE ALSO π
Kernel file ./drivers/firmware/meson/meson_sm.c, and the rest of the squad:
Go read them. It's giving "group project where everyone actually shows up" πΈ
and that's a wrap, bestie!! this page lives in ./drivers/firmware/meson, dated October 2026, and it's literally called meson_sm_call(9). mwah ππ¦β
π¦ 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