Thanks so much for your information. I tried to use this command and set "triggers" and "long_term_enable" to 0. Actually, in the definition of the triggers, there is no 0x00 but it could be set. After calling this WMI command, it returned 0 which looks like correct. But when I checked the station bf info, it still changed. I am wondering whether I can do anything to verify that. Thank you. Regards, David On Sun, Apr 22, 2018 at 10:29 AM, Dedy Lansky <dlansky@xxxxxxxxxxxxxx> wrote: > >> From: linux-wireless-owner@xxxxxxxxxxxxxxx [mailto:linux-wireless-owner@xxxxxxxxxxxxxxx] On Behalf Of David Dean Zhang >> Sent: Wednesday, April 18, 2018 9:01 PM > >> I updated the firmware and tried to call some low level functions, like WMI_PRIO_TX_SECTORS_NUMBER_CMDID and WMI_SET_RF_SECTOR_ON_CMDID . >> The previous errors have gone but it still has errors: >> wil6210 0000:03:00.0 wlp3s0: wmi_event_handle: Unhandled event 0x19a5 >> wil6210 0000:03:00.0 wlp3s0: wmi_call: wmi_call(0x09a6->0x19a6) timeout 2000 msec >> So I am wondering whether it is because the chipset does not support these wmi commands. I just want to know how to use these commands and how to disable TXSS. I appreciate if anyone could provide some suggestions. Thanks. > > This is a bug in FW that upon WMI_PRIO_TX_SECTORS_NUMBER_CMDID, wrong event is returned. Most likely that the WMI_PRIO_TX_SECTORS_NUMBER_CMDID was handled successfully. The bug is not critical - event 0x19a5 is returned instead of 0x19a6 (as can be seen in dmesg). > > Another option for disabling TXSS/BRP and hopefully to keep the sector locked is by using WMI_BF_CONTROL_CMDID. Setting "triggers" and "long_term_enable" to 0 should disable BF completely. > > Thanks, > Dedy. > > > >
