Surabhi Vishnoi <svishnoi@xxxxxxxxxxxxxx> writes:
> Refactor the code to add the support to attach htt_rx_ops
> based on HTT version.
>
> Tested HW: WCN3990
> Tested FW: WLAN.HL.3.1-00784-QCAHLSWMTPLZ-1
>
> Signed-off-by: Surabhi Vishnoi <svishnoi@xxxxxxxxxxxxxx>
[...]
> @@ -3572,7 +3580,7 @@ int ath10k_htt_txrx_compl_task(struct ath10k *ar, int budget)
> .htt_reset_paddrs_ring = ath10k_htt_reset_paddrs_ring_64,
> };
>
> -static const struct ath10k_htt_rx_ops htt_rx_ops_hl = {
> +static struct ath10k_htt_rx_ops htt_rx_ops_hl = {
> };
>
> void ath10k_htt_set_rx_ops(struct ath10k_htt *htt)
> @@ -3585,4 +3593,19 @@ void ath10k_htt_set_rx_ops(struct ath10k_htt *htt)
> htt->rx_ops = &htt_rx_ops_64;
> else
> htt->rx_ops = &htt_rx_ops_32;
> +
> + switch (ar->running_fw->fw_file.htt_op_version) {
> + case ATH10K_FW_HTT_OP_VERSION_MAIN:
> + case ATH10K_FW_HTT_OP_VERSION_10_1:
> + case ATH10K_FW_HTT_OP_VERSION_10_4:
> + htt->rx_ops->htt_fetch_peer_stats = ath10k_htt_fetch_peer_stats;
> + break;
> + case ATH10K_FW_HTT_OP_VERSION_TLV:
> + htt->rx_ops->htt_fetch_peer_stats = ath10k_htt_fetch_peer_stats_tlv;
> + break;
> + case ATH10K_FW_HTT_OP_VERSION_MAX:
> + case ATH10K_FW_HTT_OP_VERSION_UNSET:
> + WARN_ON(1);
> + return;
> + }
> }
I just realised this won't work. Let's say that there's both a qca988x
and a qca6174 PCI device on the same host. Then htt->rx_ops is shared by
_both_ devices and the htt_fetch_peer_stats field will contain the value
of the last initialised ath10k device.
So back to the drawing board. As this feature is for wcn3990 would it be
enough to modify htt_rx_ops_64? IIRC only wcn3990 support 64bit HTT
interface, right? Of course then qca6174 won't support this feature, but
does the qca6174 firmware even support that?
--
Kalle Valo
