[PATCH v2 2/2] ath10k: increase station kickout threshold

2015-03-03 Thread Rajkumar Manoharan
Since the station kickout threshold is also counting software reries (Default sw count in firmware is 16), increasing the threshold to try with atleast 20 data frames before kicking out the station. Signed-off-by: Rajkumar Manoharan --- drivers/net/wireless/ath/ath10k/core.h | 4 ++-- 1 file

Re: [PATCH 2/2] ath10k: increase station kickout threshold

2015-03-03 Thread Ben Greear
On 03/03/2015 04:20 AM, Rajkumar Manoharan wrote: Since the station kickout threshold is also counting software reries (Default sw count in firmware is 16), increasing the threshold to try with already 20 data frames before kicking out the station. Signed-off-by: Rajkumar Manoharan

[PATCH 2/2] ath10k: increase station kickout threshold

2015-03-03 Thread Rajkumar Manoharan
Since the station kickout threshold is also counting software reries (Default sw count in firmware is 16), increasing the threshold to try with already 20 data frames before kicking out the station. Signed-off-by: Rajkumar Manoharan --- drivers/net/wireless/ath/ath10k/core.h | 4 ++-- 1 file

Re: station kickout

2015-02-18 Thread Ben Greear
On 02/15/2015 05:40 AM, Kalle Valo wrote: (Adding linux-wireless) Ben Greear writes: In AP mode, it seems that 3.17-ish kernels (at least) always set station kickout to hard-coded value of 50. Is this something that should be configurable? Maybe a module parameter if nothing else? Or

Re: station kickout

2015-02-15 Thread Kalle Valo
(Adding linux-wireless) Ben Greear writes: > In AP mode, it seems that 3.17-ish kernels (at least) always set station > kickout > to hard-coded value of 50. > > Is this something that should be configurable? Maybe a module parameter > if nothing else? Or should we a