rfkill_init_sw_state(9)

📦 version 7.3.1, in nixpkgs unstable

💖 rfkill_init_sw_state — kernel API manual, bestie edition 💖

okay so this is rfkill_init_sw_state(9) from the Kernel API Manual, and it's genuinely one of those tiny functions that does exactly one job and does it iconically. no notes. let's get into it 🫶

✨ NAME ✨

rfkill_init_sw_state — initialize that persistent software block state, periodt 💅

🌸 SYNOPSIS 🌸

void rfkill_init_sw_state (struct rfkill *rfkill , bool blocked );

like, that's the whole signature. two args. beautiful. no cap.

🎀 ARGUMENTS 🎀

  • rfkill — pointer to the rfkill class to modify. yes bestie, it's a pointer, and yes it's the class you're touching 💖
  • blocked — the current software block state to set. you're literally telling it "this is the vibe rn" 🌸

🦋 DESCRIPTION 🦋

okay so picture this: some rfkill drivers preserve their software block state over power off. like they remember. main character energy fr fr. those drivers use this function to notify the rfkill core — and through that, also userspace — of their initial state. so everybody's on the same page from the jump ✨

⚠️ it should only be used before registration. that's the rule. do not come in late with this one, bestie 😭

and there's a bonus slay: it also marks the device as "persistent", which is an attribute that can be read by userspace 👑. and persistent devices? they're expected to preserve their own state when suspended. that's the whole deal, iykyk 🧚

🔥 SEE ALSO 🔥

like, the whole friend group. go read them too 💜

and that's the page!! 🎀 source/version is ./include/linux, dated October 2026 — so yeah, this manual page is coming at you straight from the kernel source tree, and it ate. mwah 💋 bye bestie!! 💖✨🦋

📦 where this page comes from