Message ID | 20210101065955.63386-1-tony@atomide.com (mailing list archive) |
---|---|
State | Accepted |
Commit | 07ceefa3012f43512e93931980bd3bdf5af96344 |
Delegated to: | Kalle Valo |
Headers | show |
Series | wlcore: Downgrade exceeded max RX BA sessions to debug | expand |
Tony Lindgren <tony@atomide.com> wrote: > We can get the following in the logs every few minutes or so: > > wlcore: ERROR exceeded max RX BA sessions > > Let's downgrade the message to a debug message as suggested by the TI > support folks at: > > https://e2e.ti.com/support/wireless-connectivity/wifi/f/968/p/352435/1244754 > > "The WL127x firmware supports max of 3 BA sessions. It cannot be increased. > I think the problem here is the peer trying to initiate a 4th BA session > (ADDBA request)." > > Signed-off-by: Tony Lindgren <tony@atomide.com> Patch applied to wireless-drivers-next.git, thanks. 07ceefa3012f wlcore: Downgrade exceeded max RX BA sessions to debug
diff --git a/drivers/net/wireless/ti/wlcore/main.c b/drivers/net/wireless/ti/wlcore/main.c --- a/drivers/net/wireless/ti/wlcore/main.c +++ b/drivers/net/wireless/ti/wlcore/main.c @@ -5391,7 +5391,7 @@ static int wl1271_op_ampdu_action(struct ieee80211_hw *hw, if (wl->ba_rx_session_count >= wl->ba_rx_session_count_max) { ret = -EBUSY; - wl1271_error("exceeded max RX BA sessions"); + wl1271_debug(DEBUG_RX, "exceeded max RX BA sessions"); break; }
We can get the following in the logs every few minutes or so: wlcore: ERROR exceeded max RX BA sessions Let's downgrade the message to a debug message as suggested by the TI support folks at: https://e2e.ti.com/support/wireless-connectivity/wifi/f/968/p/352435/1244754 "The WL127x firmware supports max of 3 BA sessions. It cannot be increased. I think the problem here is the peer trying to initiate a 4th BA session (ADDBA request)." Signed-off-by: Tony Lindgren <tony@atomide.com> --- drivers/net/wireless/ti/wlcore/main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)