lwmi_attr_id(9)
β¨ lwmi_attr_id(9) β¨
okay bestie, welcome to the kernel API manual for lwmi_attr_id β this is from the Kernel API Manual, section 9, and it's literally the little function that Formats a capability data attribute ID π
no cap, that's the whole job and it ate.
πΈ NAME πΈ
lwmi_attr_id β formats a capability data attribute ID β¨ it takes all your little IDs and squishes them into one encoded attribute ID, iconic behavior honestly π
π¦ SYNOPSIS π¦
u32 lwmi_attr_id (u8 dev_id , u8 feat_id , u8 mode_id , u8 type_id );
it hands you back a u32, and it wants four u8s in exchange. the way that's such a fair trade π«Ά
π ARGUMENTS π
dev_idβ theu8corresponding to the device ID. which device are we talking about, bestie? this one π«΅feat_idβ theu8corresponding to the feature ID on the device. the specific little feature living on that device β¨mode_idβ theu8corresponding to the wmi-gamezone mode for set/get. so likeβ¦ are we setting or getting? that's the vibe this one encodes πtype_idβ theu8corresponding to the sub-device. the sub-device!! the underling!! the main character's supporting cast π
ngl all four are u8 and all four are required β don't skip any, don't get cute with it π
β RETURN β
it returns the encoded capability data attribute ID π₯ that's it, that's the whole return value β one gloriously encoded ID, handed straight to you π
π§ SEE ALSO π§
- Kernel file
./drivers/platform/x86/lenovo/wmi-capdata.hβ go read it, iykyk ππ
and that's the whole page bestie!! π the source is from ./drivers/platform/x86/lenovo, dated October 2026, and honestly? a slay. mwah πππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms