asus_wmi_set_devstate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌟 asus_wmi_set_devstate(9) 🌟

okay bestie, welcome to the Kernel API Manual corner of the group chat πŸ’… this page is all about asus_wmi_set_devstate, and it’s giving β€œset the WMI function state” energy. no cap.


✨ NAME ✨

asus_wmi_set_devstate β€” Set the WMI function state. periodt. πŸ’–

πŸ¦‹ SYNOPSIS πŸ¦‹

int asus_wmi_set_devstate (u32 dev_id , u32 ctrl_param , u32 *retval );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev_id β€” The WMI function to call. like, which function are we poking, bestie? πŸ‘€
  • ctrl_param β€” The argument to be used for this WMI function. the little sidekick value that goes with the call ✨
  • retval β€” A pointer to where to store the value returned from WMI. it’s the spot where the WMI answer gets dropped off 🫢

⚠️ NOTE ⚠️

okay so this is important: an asus_wmi_set_devstate call must be paired with a asus_wmi_get_devstate_dsts to check if the WMI function is supported. not optional, bestie. it’s a whole must-must situation πŸ’€

πŸ”₯ RETURN πŸ”₯

  • -ENODEV β€” method ID is unsupported. like, that method said β€œnot today” πŸ™ˆ
  • 0 β€” successful and retval is filled. slay, the answer is in the pointer πŸ’…
  • other β€” error from WMI call. not every call is a main character, sometimes it’s just an error 😭

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/platform/x86/asus-wmi.c β€” go look at the source, bestie, it’s right there πŸ“
  • asus_wmi_get_devstate_dsts(9) β€” the pairing buddy from the note above 🫢

that’s the whole vibe check from the ./drivers/platform/x86 source, dated October 2026, and this is asus_wmi_set_devstate(9) signing off πŸŽ€πŸ’–βœ¨

πŸ“¦ where this page comes from