rfkill_set_hw_state_reason(9)

🦋 rfkill_set_hw_state_reason 🦋

okay bestie, welcome to the rfkill_set_hw_state_reason(9) page from the Kernel API Manual — manual name folded in right here, cute and tidy. This is the one that sets the internal rfkill hardware block state and lets you pass a reason. 💅

✨ NAME ✨

rfkill_set_hw_state_reason — set the internal rfkill hardware block state with a reason. 🎀

✨ SYNOPSIS ✨

bool rfkill_set_hw_state_reason (struct rfkill *rfkill , bool blocked ,
       enum rfkill_hard_block_reasons reason );

🌸 ARGUMENTS 🌸

• rfkill — pointer to the rfkill class to modify. 🛠️
• blocked — the current hardware block state to set. 🔒
• reason — one of enum rfkill_hard_block_reasons. 🧠

💖 DESCRIPTION 💖

Prefer to use rfkill_set_hw_state if you don't need any special reason. That's the vibe the page is giving: no special reason needed? Then bestie, go use rfkill_set_hw_state. ✨

🌈 SEE ALSO 🌈

• Kernel file ./include/linux/rfkill.h
• struct rfkill_ops(9)
• rfkill_alloc(9)
• rfkill_register(9)
• rfkill_pause_polling(9)
• rfkill_resume_polling(9)
• rfkill_unregister(9)
• rfkill_destroy(9)
• rfkill_set_hw_state(9)
• rfkill_set_sw_state(9)
• rfkill_init_sw_state(9)
• rfkill_set_states(9)
• rfkill_blocked(9)
• rfkill_soft_blocked(9)
• rfkill_find_type(9)
• rfkill_get_led_trigger_name(9)
• rfkill_set_led_trigger_name(9)

okay that's the whole page, bestie — mwah 💋. Source/version is ./include/linux, date is October 2026, and the page handle is rfkill_set_hw_state_reason(9). 🫶