armoury_get_devstate(9)

💅 armoury_get_devstate(9) — the Kernel API Manual, bestie edition ✨

okay so real talk, this page lives in the Kernel API Manual, and it's all about armoury_get_devstate — literally the function that goes and asks WMI "hey girl, what's your state?" 🎀

---

🌸 NAME 🌸

armoury_get_devstate — get the WMI function state. that's it, that's the whole vibe check 💫

---

🦋 SYNOPSIS 🦋

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

copy it exactly like that, spacing and all, no cap 🫶

---

✨ ARGUMENTS ✨

• attr — either NULL, or the kobj_attribute that's associated with the WMI function you're calling. your call bestie 💅
• retval — this one's a two-for-one deal:
  • it's a non-NULL pointer to where the value returned from WMI gets stored 👑
  • and the function presence bit is cleared in it, periodt
• dev_id — the WMI method ID to call. the main character of the argument list fr fr ⭐

---

💖 DESCRIPTION 💖

the intended usage is from a sysfs attribute, checking the associated WMI function. that's the whole plan, that's the assignment 🧚

---

🔥 RETURN 🔥

• -ENODEV — the method ID is unsupported, so like… not a thing, move on 🙈
• 0 — slay, it worked, and retval is filled 💀✨
• other — an error from the WMI call, which is giving "not our fault, blame WMI" energy 😭

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/platform/x86/asus-armoury.c 🔍
• armoury_has_devstate(9)
• armoury_set_devstate(9)
• is_power_tunable_attr(9)
• has_valid_limit(9)

go read those too, iykyk 🦋

---

lowkey important: retval needs to be non-NULL if you actually want the value back — don't come for me when there's nowhere to put it 💅

---

and that's the page!! 🎀 sign-off time: this one comes from ./drivers/platform/x86 and it's dated October 2026 — mwah, go forth and check those devstates bestie 💜🫶