Re: [PATCH ath-next v2 6/6] wifi: ath11k: Register handler for CFR capture event
Baochen Qiang <[email protected]>
| Newsgroups | org.infradead.lists.ath11k,org.kernel.vger.linux-kernel,org.kernel.vger.linux-wireless |
|---|---|
| Message-ID | <[email protected]> |
On 11/5/2025 12:26 AM, Yu Zhang(Yuriy) wrote:
> +static void ath11k_cfr_fill_hdr_info(struct ath11k *ar,
> + struct ath11k_csi_cfr_header *header,
> + struct ath11k_cfr_peer_tx_param *params)
> +{
> + header->cfr_metadata_version = ATH11K_CFR_META_VERSION_4;
> + header->cfr_data_version = ATH11K_CFR_DATA_VERSION_1;
> + header->cfr_metadata_len = sizeof(struct cfr_metadata);
> + header->chip_type = ar->ab->hw_rev;
> + header->meta_data.status = FIELD_GET(WMI_CFR_PEER_CAPTURE_STATUS,
> + params->status);
> + header->meta_data.capture_bw = params->bandwidth;
> + header->meta_data.phy_mode = params->phy_mode;
> + header->meta_data.prim20_chan = params->primary_20mhz_chan;
> + header->meta_data.center_freq1 = params->band_center_freq1;
> + header->meta_data.center_freq2 = params->band_center_freq2;
> +
> + /* CFR capture is triggered by the ACK of a QoS Null frame:
> + * - 20 MHz: Legacy ACK
> + * - 40/80/160 MHz: DUP Legacy ACK
> + */
same comment as in path 5/6
> + header->meta_data.capture_mode = params->bandwidth ?
> + ATH11K_CFR_CAPTURE_DUP_LEGACY_ACK : ATH11K_CFR_CAPTURE_LEGACY_ACK;
> + header->meta_data.capture_type = params->capture_method;
> + header->meta_data.num_rx_chain = ar->num_rx_chains;
> + header->meta_data.sts_count = params->spatial_streams;
> + header->meta_data.timestamp = params->timestamp_us;
> + ether_addr_copy(header->meta_data.peer_addr, params->peer_mac_addr);
> + memcpy(header->meta_data.chain_rssi, params->chain_rssi,
> + sizeof(params->chain_rssi));
> + memcpy(header->meta_data.chain_phase, params->chain_phase,
> + sizeof(params->chain_phase));
> + memcpy(header->meta_data.agc_gain, params->agc_gain,
> + sizeof(params->agc_gain));
> +}
> +