wkup_m3_request_pm_status(9)

📦 version 7.3.1, in nixpkgs unstable

💅 wkup_m3_request_pm_status — the Kernel API Manual tea 🎀

okay so bestie, welcome to the wkup_m3_request_pm_status(9) page 💖 this one lives in the Kernel API Manual, and it's short, it's sweet, and it's literally the "did my nap work" check for the wakeup M3. let's get into it ✨

🌸 NAME 🌸

wkup_m3_request_pm_status — grab the wkup_m3 status code after a suspend, bestie 🫶

✨ SYNOPSIS ✨

int wkup_m3_request_pm_status (struct wkup_m3_ipc *m3_ipc );

like, that's the whole call. one argument, one int back, no drama 💅

🦋 ARGUMENTS 🦋

  • m3_ipc — pointer to the wkup_m3_ipc context 👑 that's your handle to the whole wkup_m3 ipc vibe, and yeah, you gotta hand it over.

🔥 DESCRIPTION 🔥

so what does it actually do? it returns a code representing the status of a low power mode transition 🌈 like, the receipt for the nap your system just took.

the values are giving very much "did it work or not":

  • 0 — successful transition ✅ slay, the low power state happened
  • 1 — failure to transition to low power state 😭 it did not go night-night

no cap, that's the entire mapping. 0 good, 1 not good. iconic minimalism tbh 🎀

💜 SEE ALSO 💜

peep the kernel file ./drivers/soc/ti/wkup_m3_ipc.c for the whole friend group 🧚 and then go say hi to the rest of the wkup_m3 crew:

💀 friendly reminder: 0 means the transition worked, 1 means it didn't. don't flip those in your head, bestie, i'm begging 🙈

okay that's the page!! this one's coming at you from ./drivers/soc/ti 🌸 and it's dated October 2026 — mwah, go touch some registers, love u, bye 💖✨🦋

📦 where this page comes from