ath11k_cfr_c...te_and_relay(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ath11k_cfr_correlate_and_relay β€” the Kernel API Manual moment πŸŽ€

okay so bestie, this is a page straight out of the Kernel API Manual, and it's genuinely iconic: ath11k_cfr_correlate_and_relay is the function that plays matchmaker for CFR events. she matches, she relays, she does NOT let orphan events just sit there. periodt. ✨


🌸 NAME 🌸

ath11k_cfr_correlate_and_relay β€” correlate and relay CFR events, no cap 🫢


✨ SYNOPSIS ✨

enum ath11k_cfr_correlate_status ath11k_cfr_correlate_and_relay (struct
ath11k *ar , struct ath11k_look_up_table *lut , u8 event_type );

like yes, she takes three things and gives you back a status. main character energy fr fr πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • ar β€” Pointer to ath11k structure. the whole ath11k vibe lives here 🏠
  • lut β€” Lookup table for correlation. this is the little matchmaking directory she consults πŸ‘€
  • event_type β€” Type of event received (TX or DBR). she needs to know which flavor of event just walked in πŸšͺ

πŸ’– DESCRIPTION πŸ’–

so what she actually does: she correlates WMI_PDEV_DMA_RING_BUF_RELEASE_EVENT (that's DBR) with WMI_PEER_CFR_CAPTURE_EVENT (that's TX capture) by PPDU ID. yup, PPDU ID matchmaking, it's giving dating app but for kernel events πŸ˜­πŸ’˜

If both events are present and the PPDU IDs match, she returns CORRELATE_STATUS_RELEASE to relay the correlated data to userspace. slay β€” the data gets to go to the party πŸŽ‰πŸ”₯

Otherwise she returns CORRELATE_STATUS_HOLD to wait for the other event. not ghosting, just… waiting for her other half to show up πŸ™ˆ

She also checks pending DBR events and clears them when no corresponding TX capture event is received for the PPDU. so yes, she cleans up after herself β€” no stale event buildup, we love a tidy queen πŸ‘‘βœ¨


⭐ RETURN ⭐

CORRELATE_STATUS_RELEASE or CORRELATE_STATUS_HOLD β€” that's it, that's the whole answer πŸŽ€


🌈 SEE ALSO 🌈

  • Kernel file ./drivers/net/wireless/ath/ath11k/cfr.c πŸ’œ

ngl if you're poking at CFR correlation, go read that cfr.c file β€” she's the whole source of truth, bestie πŸ“

and that's the page!! brought to you by the fine folks at ./drivers/net/wireless/ath/ath11k, dated October 2026 β€” go off, kernel docs, you ate πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from