On 23 June 2016 at 18:40, Mohammed Shafi Shajakhan <[email protected]> wrote: > From: Mohammed Shafi Shajakhan <[email protected]> > > For chipsets like QCA99X0, IPQ4019 and later we are not getting proper > NULL func status (always acked/successs !!) when hostapd does a > PROBE_CLIENT via nullfunc frames when the station is powered off > abruptly (inactive timer probes client via null func after the inactive > time reaches beyond the threshold). Fix this by disabling the workaround > (getting the ACK status of NULL func frames by sending via HTT mgmt-tx > path) introduced by the change ("ath10k: fix beacon loss handling ") > for QCA99X0 and later chipsets. The normal tx path provides the proper > ACK status for NULL data frames. As of now disable this workaround for > chipsets QCA99X0 and later, once the 10.1 firmware is obselete we can > completely get rid of this workaround for all the chipsets > > Signed-off-by: Tamizh chelvam <[email protected]> > Signed-off-by: Mohammed Shafi Shajakhan <[email protected]> > --- > drivers/net/wireless/ath/ath10k/core.c | 3 +++ > drivers/net/wireless/ath/ath10k/core.h | 6 ++++++ > drivers/net/wireless/ath/ath10k/mac.c | 1 + > 3 files changed, 10 insertions(+) > > diff --git a/drivers/net/wireless/ath/ath10k/core.c > b/drivers/net/wireless/ath/ath10k/core.c > index 689d6ce..9978e4a 100644 > --- a/drivers/net/wireless/ath/ath10k/core.c > +++ b/drivers/net/wireless/ath/ath10k/core.c > @@ -181,6 +181,7 @@ static const struct ath10k_hw_params > ath10k_hw_params_list[] = { > .board = QCA99X0_HW_2_0_BOARD_DATA_FILE, > .board_size = QCA99X0_BOARD_DATA_SZ, > .board_ext_size = QCA99X0_BOARD_EXT_DATA_SZ, > + .disable_null_func_workaround = true,
Tx completion (bugs) are firmware specific, not hardware. This should be expressed via features bits in ath10k FW API, no? Michał _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
