module_param_hw_named(9)

✨ module_param_hw_named ✨

okay bestie, so this one is a Kernel API Manual page and it's literally all about module_param_hw_named — a parameter that represents a hw parameter 💅 no cap, that's the whole vibe. let's get into it 🫶

🌸 SYNOPSIS 🌸

module_param_hw_named (name , value , type , hwtype , perm );

that's the whole call, bestie — five args, in that exact order, periodt ✨

🎀 ARGUMENTS 🎀

• name — a valid C identifier which is the parameter name. like, it has to actually be a legal C identifier, okay? no funny business 🙈
• value — the actual lvalue to alter. yes, the actual thing that gets changed 🔥
• type — the type of the parameter.
• hwtype — what the value represents (enum hwparam_type). that's the whole point of the hw in the name, iykyk 👑
• perm — visibility in sysfs. that's your sysfs visibility setting, no more no less 💖

🦋 DESCRIPTION 🦋

okay so normally it's a good idea to have your variable names and your user-exposed names be the same — like, matching, cute, clean, very cohesive ✨. but that gets harder if the variable must be non-static, or if it lives inside a structure 😭. and this is the icon that fixes that: it allows exposure under a different name 💅

🌈 SEE ALSO 🌈

• Kernel file ./include/linux/moduleparam.h
• module_param(9)
• module_param_unsafe(9)
• module_param_named(9)
• module_param_named_unsafe(9)
• module_param_cb(9)
• core_param_cb(9)
• postcore_param_cb(9)
• arch_param_cb(9)
• subsys_param_cb(9)
• fs_param_cb(9)
• device_param_cb(9)
• late_param_cb(9)
• core_param(9)
• core_param_unsafe(9)
• __core_param_cb(9)
• module_param_string(9)
• parameq(9)
• parameqn(9)
• module_param_array(9)
• module_param_array_named(9)
• module_param_hw_array(9)

like, that's the whole friend group right there — go read them too, they're all slaying in their own way 🧚💜

bestie note: the source path is ./include/linux and this page is dated October 2026 — that's the version/date sign-off, so now you know where it came from and when, mwah 💋🍓