From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: "Yu Zhang(Yuriy)" <yu.zhang@oss.qualcomm.com>, jjohnson@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
ath11k@lists.infradead.org,
Vasanthakumar Thiagarajan
<vasanthakumar.thiagarajan@oss.qualcomm.com>
Subject: Re: [PATCH ath-next v2 6/6] wifi: ath11k: Register handler for CFR capture event
Date: Wed, 5 Nov 2025 10:49:45 +0800 [thread overview]
Message-ID: <52b34262-ed22-43a1-b6dd-cea37c33d627@oss.qualcomm.com> (raw)
In-Reply-To: <20251104162633.3007874-7-yu.zhang@oss.qualcomm.com>
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));
> +}
> +
prev parent reply other threads:[~2025-11-05 2:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 16:26 [PATCH ath-next v2 0/6] wifi: ath11k: Add single shot/periodic CFR capture support Yu Zhang(Yuriy)
2025-11-04 16:26 ` [PATCH ath-next v2 1/6] wifi: ath11k: Add initialization and deinitialization sequence for CFR module Yu Zhang(Yuriy)
2025-11-05 2:40 ` Baochen Qiang
2025-11-04 16:26 ` [PATCH ath-next v2 2/6] wifi: ath11k: Register debugfs for CFR configuration Yu Zhang(Yuriy)
2025-11-04 16:26 ` [PATCH ath-next v2 3/6] wifi: ath11k: Add support unassociated client CFR Yu Zhang(Yuriy)
2025-11-04 16:26 ` [PATCH ath-next v2 4/6] wifi: ath11k: Register relayfs entries for CFR dump Yu Zhang(Yuriy)
2025-11-04 16:26 ` [PATCH ath-next v2 5/6] wifi: ath11k: Register DBR event handler for CFR data Yu Zhang(Yuriy)
2025-11-05 2:46 ` Baochen Qiang
2025-11-04 16:26 ` [PATCH ath-next v2 6/6] wifi: ath11k: Register handler for CFR capture event Yu Zhang(Yuriy)
2025-11-05 2:49 ` Baochen Qiang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52b34262-ed22-43a1-b6dd-cea37c33d627@oss.qualcomm.com \
--to=baochen.qiang@oss.qualcomm.com \
--cc=ath11k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=vasanthakumar.thiagarajan@oss.qualcomm.com \
--cc=yu.zhang@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox