cfg80211_chandef_dfs_usable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cfg80211_chandef_dfs_usable(9)

okay so bestie, welcome to the Kernel API Manual ✨ β€” this one's a little function with a big job and honestly? it's giving gatekeeper energy. let's get into it πŸŽ€


✨ NAME ✨

cfg80211_chandef_dfs_usable β€” checks if chandef is DFS usable and we can/need start CAC on such channel πŸ¦‹

like, it's literally the vibe check for whether a channel definition is DFS-usable and whether we can or need to start CAC on that channel, iykyk πŸ’…


🌸 SYNOPSIS 🌸

bool cfg80211_chandef_dfs_usable (struct wiphy *wiphy , const struct
       cfg80211_chan_def *chandef );

returns a bool, takes two pointers, no cap 🫢


πŸ‘‘ ARGUMENTS πŸ‘‘

  • wiphy β€” the wiphy to validate against πŸ”₯ like, this is the thing we're checking everything against, the main character, the reference point
  • chandef β€” the channel definition to check πŸ’– the actual channel sitch you're asking about

⭐ RETURN ⭐

true if all channels available and at least one channel requires CAC (NL80211_DFS_USABLE) πŸ’€βœ¨

so like β€” all channels gotta be available, and at least one of them has to require CAC. both. together. that's the combo that gets you a true, periodt πŸ‘‘

careful bestie: it's not true for just anything β€” the all-channels-available part AND the at-least-one-requires-CAC part both have to be true. that's literally the whole point of the function πŸ™ˆ

that's part 1, more incoming 🌈

✨ SEE ALSO ✨

okay bestie, so this is the part where the page shows you everyone else in the friend group πŸ’… and no, I'm not gonna skip any of them, because there are literally like 359 of these and each one is a real cross-reference you might actually need. every single name below is written exactly how it appears, (9) and all β€” that's just how these are spelled here, don't come for me 🫢

the header itself lives at Kernel file ./include/net/cfg80211.h, and the soft intro pages are Introduction(9) and Device registration(9) β€” start there if you're brand new, no cap.


πŸŽ€ the channel / band / rate besties

yes, _ieee80211_set_sband_iftype_data(9) really does have that little underscore in front. it's not a typo, it's just the shy one πŸ™ˆ

🌸 actions & configuration era

  • Actions and configuration(9), struct vif_params(9), struct key_params(9), struct cfg80211_chan_def(9), struct cfg80211_tid_cfg(9), struct cfg80211_tid_config(9), struct cfg80211_fils_aad(9), struct cfg80211_set_hw_timestamp(9)

πŸ’œ the whole chandef cinematic universe

like, that's the family this page belongs to fr fr β€” you literally saw cfg80211_chandef_usable(9) up in the synopsis and now here's all its siblings πŸ’–


πŸ¦‹ survey, AP, beacons & friends

  • enum survey_info_flags(9), struct survey_info(9), struct cfg80211_crypto_settings(9), struct cfg80211_mbssid_config(9), struct cfg80211_mbssid_elems(9), struct cfg80211_rnr_elems(9), struct cfg80211_beacon_data(9), struct cfg80211_acl_data(9), struct cfg80211_fils_discovery(9), struct cfg80211_unsol_bcast_probe_resp(9), struct cfg80211_s1g_short_beacon(9), struct cfg80211_ap_settings(9), struct cfg80211_ap_update(9), struct cfg80211_csa_settings(9), struct cfg80211_color_change_settings(9), struct iface_combination_params(9)

⭐ station, rates & stats

  • enum station_parameters_apply_mask(9), struct sta_txpwr(9), struct link_station_parameters(9), struct link_station_del_parameters(9), struct cfg80211_ttlm_params(9), struct station_parameters(9), struct station_del_parameters(9), enum cfg80211_station_type(9), cfg80211_check_station_change(9), enum rate_info_flags(9), enum rate_info_bw(9), struct rate_info(9), enum bss_param_flags(9), struct sta_bss_parameters(9), struct cfg80211_txq_stats(9), struct cfg80211_tid_stats(9), struct link_station_info(9), struct station_info(9)

πŸ“ SAR, monitor, mesh, OCB & txq

  • struct cfg80211_sar_sub_specs(9), struct cfg80211_sar_specs(9), struct cfg80211_sar_freq_ranges(9), struct cfg80211_sar_capa(9), cfg80211_get_station(9), enum monitor_flags(9), enum mpath_info_flags(9), struct mpath_info(9), enum wiphy_bss_param_flags(9), struct bss_parameters(9), struct mesh_config(9), struct mesh_setup(9), struct ocb_setup(9), struct ieee80211_txq_params(9)

🧚 scanning & BSS list handling (a whole moment)

  • Scanning and BSS list handling(9), struct cfg80211_ssid(9), struct cfg80211_scan_info(9), struct cfg80211_scan_6ghz_params(9), struct cfg80211_scan_request(9), struct cfg80211_match_set(9), struct cfg80211_sched_scan_plan(9), struct cfg80211_bss_select_adjust(9), struct cfg80211_sched_scan_request(9), enum cfg80211_signal_type(9), struct cfg80211_inform_bss(9), struct cfg80211_bss_ies(9), struct cfg80211_bss(9), ieee80211_bss_get_elem(9), ieee80211_bss_get_ie(9)

πŸŽ€ auth, assoc & connect structs

  • struct cfg80211_auth_request(9), struct cfg80211_assoc_link(9), struct cfg80211_ml_reconf_req(9), enum cfg80211_assoc_req_flags(9), struct cfg80211_assoc_request(9), struct cfg80211_deauth_request(9), struct cfg80211_disassoc_request(9), struct cfg80211_ibss_params(9), struct cfg80211_bss_selection(9), struct cfg80211_connect_params(9), enum cfg80211_connect_params_changed(9), enum wiphy_params_flags(9), struct cfg80211_pmksa(9)

πŸ’… patterns, wowlan, coalesce & qos

  • struct cfg80211_pkt_pattern(9), struct cfg80211_wowlan_tcp(9), struct cfg80211_wowlan(9), struct cfg80211_coalesce_rules(9), struct cfg80211_coalesce(9), struct cfg80211_wowlan_nd_match(9), struct cfg80211_wowlan_nd_info(9), struct cfg80211_wowlan_wakeup(9), struct cfg80211_gtk_rekey_data(9), struct cfg80211_update_ft_ies_params(9), struct cfg80211_mgmt_tx_params(9), struct cfg80211_dscp_exception(9), struct cfg80211_dscp_range(9), struct cfg80211_qos_map(9)

πŸ”₯ NAN (Neighbor Awareness Networking) corner

  • Neighbor Awareness Networking (NAN)(9), struct cfg80211_nan_band_config(9), struct cfg80211_nan_conf(9), struct cfg80211_nan_channel(9), struct cfg80211_nan_local_sched(9), struct cfg80211_nan_peer_map(9), struct cfg80211_nan_peer_sched(9), enum cfg80211_nan_conf_changes(9), struct cfg80211_nan_func_filter(9), struct cfg80211_nan_func(9)

🫢 PMK, external auth, FTM/PMSR & OWE

  • struct cfg80211_pmk_conf(9), struct cfg80211_external_auth_params(9), struct cfg80211_ftm_responder_stats(9), struct cfg80211_pmsr_ftm_result(9), struct cfg80211_pmsr_result(9), struct cfg80211_pmsr_ftm_request_peer(9), struct cfg80211_pmsr_request_peer(9), struct cfg80211_pmsr_request(9), struct cfg80211_update_owe_info(9), struct mgmt_frame_regs(9)

πŸ‘‘ ops, wiphy capabilities & combinations

  • struct cfg80211_ops(9), enum wiphy_flags(9), struct ieee80211_iface_limit(9), struct ieee80211_iface_combination(9), enum wiphy_wowlan_support_flags(9), struct wiphy_wowlan_support(9), struct wiphy_coalesce_support(9), enum wiphy_vendor_command_flags(9), enum wiphy_opmode_flag(9), struct sta_opmode_info(9), struct wiphy_vendor_command(9), struct wiphy_iftype_ext_capab(9), cfg80211_get_iftype_ext_capa(9), struct cfg80211_pmsr_capabilities(9), struct wiphy_iftype_akm_suites(9), struct wiphy_radio_cfg(9), struct wiphy_radio_freq_range(9), struct wiphy_radio(9), enum wiphy_nan_flags(9), struct wiphy_nan_capa(9)

🌈 the wiphy lifecycle & locking girlies

πŸ’œ wireless_dev trio


✨ utility functions (the glow-up section)

πŸ¦‹ data path helpers & element finders


🌸 regulatory enforcement infrastructure

πŸŽ€ scan done, BSS informing & refcounting

__cfg80211_get_bss(9) has two underscores up front, and yes that means it's the lowkey internal one, respect the naming convention 😌

πŸ”₯ mlme notifications & failures


πŸ’€ rfkill, vendor commands & test mode

⭐ connect / roam / disconnect results

🫢 station add/del & tid stats

🌈 the notify-everyone section (cqm, radar, cac & co.)


and that's literally where this part stops β€” the list just keeps going in the next chunk, so don't go anywhere πŸ§šβ€β™€οΈ

...and the list just keeps going, bestie. Like genuinely, the see-also section here is doing the absolute most πŸ’… so here's the whole rest of the crew, in order, no skips:


okay that's literally the whole page, bestie, we made it πŸŽ€ Take a sip of water, you've earned it.

This one's shipped straight out of ./include/net, dated October 2026, and it's the cfg80211_chandef_dfs_usable(9) page β€” go forth and check those DFS channel definitions responsibly, iykyk πŸ’œ

πŸ“¦ where this page comes from