[PATCH v2] ath10k: Report low ack rssi based on the reason code

Firmware sends peer sta kickout event to the driver along with the reason code for a particular peer. Currently the sta kickout event is delivered to the upper layer without checking if the reason code is valid or not. This causes frequent disconnection of the STA. Report low ack rssi event to ma

Re: [PATCH v2] ath10k: Report low ack rssi based on the reason code

On 04/03/2019 12:23 AM, Rakesh Pillai wrote: > Firmware sends peer sta kickout event to the driver > along with the reason code for a particular peer. > > Currently the sta kickout event is delivered to the > upper layer without checking if the reason code is > valid or not. This causes frequent

Re: [PATCH v2] ath10k: Report low ack rssi based on the reason code

Peter Oh writes: > On 04/03/2019 12:23 AM, Rakesh Pillai wrote: >> Firmware sends peer sta kickout event to the driver >> along with the reason code for a particular peer. >> >> Currently the sta kickout event is delivered to the >> upper layer without checking if the reason code is >> valid or n

Re: FW: [PATCH v2] ath10k: Report low ack rssi based on the reason code

diff --git a/drivers/net/wireless/ath/ath10k/wmi.h b/drivers/net/wireless/ath/ath10k/wmi.h index e1c40bb..3ccd79e 100644 --- a/drivers/net/wireless/ath/ath10k/wmi.h +++ b/drivers/net/wireless/ath/ath10k/wmi.h @@ -6797,6 +6797,8 @@ struct wmi_vdev_start_ev_arg { struct wmi_peer_kick_ev_arg {