meson_sm_call(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’œ 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