asus_wmi_get_devstate_dsts(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… asus_wmi_get_devstate_dsts(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual ✨ this one's a little function from the ASUS WMI squad and honestly? she's a whole vibe. her name is asus_wmi_get_devstate_dsts and she's here to get the WMI function state for you. lowkey iconic of her.


✨ NAME ✨

asus_wmi_get_devstate_dsts β€” get the WMI function state. that's it, that's the whole job πŸŽ€


🌸 SYNOPSIS 🌸

int asus_wmi_get_devstate_dsts (u32 dev_id , u32 *retval );

like look at her, only two arguments, she's not asking for much 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev_id β€” the WMI method ID to call. this is the "which thing do you want" number, so pick it carefully bestie πŸ’…
  • retval β€” a pointer to where to store the value returned from WMI. it's the lil bucket you're handing her so she can drop the answer in it πŸ“

⭐ RETURN ⭐

she gives you back an int, and here's how to read it, no cap:

  • -ENODEV β€” the method ID is unsupported. basically she looked at your dev_id and was like "girl. no." 😭
  • 0 β€” successful, and retval is filled. slay, the bucket has data now πŸ’–
  • other β€” an error from the WMI call itself. not her fault, the WMI call fumbled πŸ™ˆ

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/platform/x86/asus-wmi.c
  • asus_wmi_set_devstate(9) β€” the setter sister, go check her out too πŸ‘‘

so yeah, that's the whole page. no cap, she's a simple queen: you give her an ID and a pointer, she gives you a state and maybe an error. vibe check passed ✨

this little drop came to you from ./drivers/platform/x86, dated October 2026 β€” mwah, kisses from the kernel, bye bestie πŸ§šπŸ’œ

πŸ“¦ where this page comes from