rfkill_set_sw_state(9)

🎀 rfkill_set_sw_state 🎀

okay so bestie, this is the Kernel API Manual page for rfkill_set_sw_state, and it's literally about setting the internal rfkill software block state. no cap, that's the whole assignment. 💅

🌸 NAME 🌸

rfkill_set_sw_state — Set the internal rfkill software block state. iconic, concise, we love her.

✨ SYNOPSIS ✨

bool rfkill_set_sw_state (struct rfkill *rfkill , bool blocked );

🎀 ARGUMENTS 🎀

• rfkill — pointer to the rfkill class to modify. that's the thing you're touching, bestie.
• blocked — the current software block state to set. the state you're serving up.

💅 DESCRIPTION 💅

rfkill drivers that get events when the soft-blocked state changes — yes, some platforms directly act on input but allow changing again — use this function to notify the rfkill core (and through that also userspace) of the current state. communication queen behavior. 💖

Drivers should also call this function after resume if the state has been changed by the user. This only makes sense for "persistent" devices (see rfkill_init_sw_state). iykyk.

This function can be called in any context, even from within rfkill callbacks. flexible, unbothered, moisturised. ✨

The function returns the combined block state (true if transmitter should be blocked). so true means block that transmitter, periodt.

🦋 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_reason(9), rfkill_set_hw_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)

mwah 💋 this page's source/version is ./include/linux, it's dated October 2026, and it's the rfkill_set_sw_state(9) entry from the Kernel API Manual. byeee bestie 🫶🌸