Bluetooth: Don't send RNR immediately when entering local busy
authorSzymon Janc <szymon.janc@tieto.com>
Wed, 11 Jan 2012 09:59:48 +0000 (10:59 +0100)
committerJohan Hedberg <johan.hedberg@intel.com>
Mon, 13 Feb 2012 15:01:26 +0000 (17:01 +0200)
commit77f918bc7babb8473933ca0a6deefc64fe24b06c
tree100f432f8fc48be2f871e7515b04be62e928e8e2
parentb17e73bb4269f47e1ea2d64a834f1cfc8644fabb
Bluetooth: Don't send RNR immediately when entering local busy

There is no need to send RNR immediately when entring local busy.
Also upper layer might clear local busy condition before ack timer
expires saving few cycles for sending RNR.

This also prevents sending two RNRs in some cases where sending one
would be enough i.e received N I-frame can trigger local busy
(sending RNR acking up to N-1 I-frame) and later sending ack (RNR
acking up to N I-frame).

This was affecting TC_ERM_BV_07_C and TC_ERM_BV_22_C with some non
default channel parameters (tx window and receiving buffer sizes).

Signed-off-by: Szymon Janc <szymon.janc@tieto.com>
Acked-by: Marcel Holtmann <marcel@holtmann.org>
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
net/bluetooth/l2cap_core.c