wiphy_hrtimer_work_pending(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… wiphy_hrtimer_work_pending(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” this one's about wiphy_hrtimer_work_pending, and yes it's a whole mouthful, we're gonna get through it together 🫢


✨ NAME ✨

wiphy_hrtimer_work_pending β€” literally just: find out whether a wiphy hrtimer work item is currently pending. that's it. that's the whole vibe check πŸ”₯


✨ SYNOPSIS ✨

bool wiphy_hrtimer_work_pending (struct wiphy *wiphy , struct
wiphy_hrtimer_work *hrwork );

so it takes two things and gives you back a bool, no cap ✨


✨ ARGUMENTS ✨

  • wiphy β€” the wiphy in question πŸ’« and like, heads up: it's there for debug purposes. that's its whole job bestie, don't ask it for more.
  • hrwork β€” the hrtimer work in question πŸŽ€ the actual one you're checking on.

✨ RETURN ✨

  • true β€” if timer is pending πŸ‘‘
  • false β€” otherwise πŸ™ˆ

✨ DESCRIPTION ✨

okay so this page is lowkey short and it's giving "go read the other one" energy β€” and honestly? respectfully? it says please refer to the wiphy_delayed_work_pending documentation, because this function is the equivalent function for hrtimer based delayed work items. so like, same idea, different timer flavor 🧚


more coming bestie, stay tuned πŸ’–

✨ SEE ALSO ✨

okay bestie, this is the part where the manpage just dumps the entire extended friend group on you 😭 like it's not going to introduce them one by one, it's just gonna say "here's everybody, go say hi." And honestly? Respect. So let's give them all their little moment, in the exact order the page lists them, because we do not skip people in this house πŸ’…

Starting with the source of truth itself, the kernel file ./include/net/cfg80211.h, and the intro docs:

Then we roll into the config era β€” this is where all the "what can you actually do to a wiphy" lives:

like, that's a lot of chandef content and I'm obsessed with how thorough it is πŸŽ€

  • 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)
  • 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)
  • 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)

and now we hit the scanning era, aka the "where did my BSS go" zone:

  • 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)
  • 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), 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)

okay NAN time, the little side quest section πŸ¦‹:

  • 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)
  • 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)
  • 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)

and then the wiphy lifecycle crew, which β€” not me realizing this is literally our homegirl's family tree 😭:

yes bestie, wiphy_hrtimer_work_flush(9) is right there in the same list as the function you're reading about β€” that's the full trio, queue/cancel/flush, plus the wiphy_delayed_work_pending(9) cousin. Go read them all, it's giving "family reunion" 🫢

Then the wireless_dev bit and utility functions, where stuff gets genuinely useful:

data path helpers next, where packets get handled and headers get stripped 🧚:

regulatory enforcement, the ✨rules are rules✨ section:

then scan/BSS notification helpers and the mlme mgmt crowd:

RFkill integration, short but iconic:

vendor commands & test mode, the "oem stuff" corner 🌸:

and then the connection/roaming notification gang, besties who just want to tell you what happened:

and that's the entire list, bestie β€” every single reference, nothing skipped, nothing merged, no cap πŸ’– if a name is in the original page it's in this list too, so you can literally just scroll and find your fave. slay ✨

…and the rest of the crew rolls in like the group chat when someone says "we're getting boba" πŸ’– keep scrolling, bestie, they're all here:

the regulatory girlies πŸ’…

channel switch moment ✨

operating class / chandef girlies (they always come in fours) πŸŽ€

registration & friends πŸ¦‹

fast transition things 🌸

P2P + IE parsing squad πŸ”₯

wakeups, crit proto, channel counting 😭

combination checking besties 🧚

shutting it all down (respectfully) πŸ’€

ext feature icons πŸ‘‘

the whole rest of the function list, no cap 🫢

bestie that is a lot of cross-references, but they're all exactly as written, so go click through them and slay your kernel spelunking πŸ’œ

okay that's the whole page, mwah πŸ’‹ this lil icon lives at ./include/net (that's the source path, iykyk) and it's stamped October 2026, and the page itself is wiphy_hrtimer_work_pending(9) β€” go forth and be the main character of your own hrtimer work, bestie πŸŽ€βœ¨

πŸ“¦ where this page comes from