armoury_set_devstate(9)

✨ armoury_set_devstate(9) ✨

okay bestie, welcome to armoury_set_devstate — it's from the Kernel API Manual and it's the function that actually sets your WMI function state 💅 like it's the whole vibe check for writing values, no cap.

---

🌸 NAME 🌸

armoury_set_devstate — set the WMI function state, periodt.

---

🎀 SYNOPSIS 🎀

int armoury_set_devstate (struct kobj_attribute *attr , u32 value , u32
*retval , u32 dev_id );

---

🦋 ARGUMENTS 🦋

• attr — the kobj_attribute that's tied to the WMI function being called. it's giving "the handle for the thing you're poking" 🫶
• value — the shiny new value you wanna set ✨
• retval — where you stash the value coming back from WMI, or NULL if you literally don't care. your call bestie 🙈
• dev_id — the WMI method ID to call — the actual address of the function, iykyk 📇

---

💖 DESCRIPTION 💖

so the intended usage is from the sysfs attribute setting that's associated with the WMI function. and before you call this, you gotta check that the function is even present first — vibe check the function before you use it, fr fr 🔥

every single WMI write MUST go through this function to enforce the safety checks. not "most", not "usually" — every. no skipping, no shortcuts, no "not me" energy 😭 this is the main character of WMI writes 👑

and here's the tea ☕: a result of !1 is usually considered a fail by ASUS. usually. but some WMI methods (like eGPU or CPU cores, iconic exceptions that they are) do use > 1 to return a status code or similar. in these cases the caller is interested in the actual return value and should perform the relevant checks themselves 💅 so like, read the room and check what your method does.

---

⭐ RETURN ⭐

• -EINVAL — attempt to set a dangerous or unsupported value 💀 like bestie no, that's not allowed
• -EIO — the WMI function returned an error 😭 it did not slay
• 0 — successful and retval is filled 🎉 ate and left no crumbs
• other — an error from the WMI call, go investigate 🕵️‍♀️

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/platform/x86/asus-armoury.c — the source, go read it 🧚
• armoury_has_devstate(9)
• armoury_get_devstate(9)
• is_power_tunable_attr(9)
• has_valid_limit(9)

---

🦋 okay that's the whole page bestie, you're officially educated. this lil cutie lives in ./drivers/platform/x86 and the version tag says October 2026 — go forth, set those devstates safely, and remember: presence check first, always 💜🎀✨