ath11k: trigger frame types

Hello wireless devs,

I am currently learning about the topic of “Trigger Frames” and analyzing
the packets I captured with Wireshark. I am using the QCN9074 with the
`ath11k` driver and set up an AP with HE80, to which two clients (STA1 and
STA2) are connected. When I analyze the packets, I can see BSRP and MU‑BAR
trigger frames. What is interesting, however, is the output of htt_stats:

    $ echo 12 > htt_stats_type
    $ cat htt_stats
    HTT_TX_SELFGEN_CMN_STATS_TLV:
    mac_id = 0
    su_bar = 238
    rts = 0
    cts2self = 0
    qos_null = 0
    delayed_bar_1 = 0
    delayed_bar_2 = 0
    delayed_bar_3 = 0
    delayed_bar_4 = 0
    delayed_bar_5 = 0
    delayed_bar_6 = 0
    delayed_bar_7 = 0

    HTT_TX_SELFGEN_AC_STATS_TLV:
    ac_su_ndpa = 0
    ac_su_ndp = 0
    ac_mu_mimo_ndpa = 0
    ac_mu_mimo_ndp = 0
    ac_mu_mimo_brpoll_1 = 0
    ac_mu_mimo_brpoll_2 = 0
    ac_mu_mimo_brpoll_3 = 0

    HTT_TX_SELFGEN_AX_STATS_TLV:
    ax_su_ndpa = 234
    ax_su_ndp = 234
    ax_mu_mimo_ndpa = 0
    ax_mu_mimo_ndp = 0
    ax_mu_mimo_brpoll_1 = 0
    ax_mu_mimo_brpoll_2 = 0
    ax_mu_mimo_brpoll_3 = 0
    ax_mu_mimo_brpoll_4 = 0
    ax_mu_mimo_brpoll_5 = 0
    ax_mu_mimo_brpoll_6 = 0
    ax_mu_mimo_brpoll_7 = 0
    ax_basic_trigger = 0
    ax_ulmumimo_trigger = 0
    ax_bsr_trigger = 0
    ax_mu_bar_trigger = 0
    ax_mu_rts_trigger = 0

    HTT_TX_SELFGEN_AC_ERR_STATS_TLV:
    ac_su_ndp_err = 0
    ac_su_ndpa_err = 0
    ac_mu_mimo_ndpa_err = 0
    ac_mu_mimo_ndp_err = 0
    ac_mu_mimo_brp1_err = 0
    ac_mu_mimo_brp2_err = 0
    ac_mu_mimo_brp3_err = 0

    HTT_TX_SELFGEN_AX_ERR_STATS_TLV:
    ax_su_ndp_err = 97
    ax_su_ndpa_err = 0
    ax_mu_mimo_ndpa_err = 0
    ax_mu_mimo_ndp_err = 0
    ax_mu_mimo_brp1_err = 0
    ax_mu_mimo_brp2_err = 0
    ax_mu_mimo_brp3_err = 0
    ax_mu_mimo_brp4_err = 0
    ax_mu_mimo_brp5_err = 0
    ax_mu_mimo_brp6_err = 0
    ax_mu_mimo_brp7_err = 0
    ax_basic_trigger_err = 0
    ax_ulmumimo_trigger_err = 0
    ax_bsr_trigger_err = 45
    ax_mu_bar_trigger_err = 238
    ax_mu_rts_trigger_err = 0

I am wondering why the error counter keeps increasing even though the
packets are there. Maybe I am simply misinterpreting the firmware
statistics here.

It is quite difficult for me to set up an environment where I can reliably
receive specific trigger frames. Is there any way in `ath11k`, or in the
firmware via WMI commands, to force certain trigger frames or restrict the
use of specific ones?


Best regards
Alexander Wilhelm