Bluetooth: ATT: remove BT_ATT_ENFORCE_FLOW
Enforcing the peer's behavior is not strictly necessary. All the host should do is make sure it is resilient to a spec-violating peer. Moreover, a growing number of platforms were disabling the check, as the spec allows "batching" HCI num complete packets events, stalling ATT RX. Signed-off-by: Jonathan Rico <jonathan.rico@nordicsemi.no> Co-authored-by: Aleksander Wasaznik <aleksander.wasaznik@nordicsemi.no>
This commit is contained in:
parent
b68987fe9e
commit
ea04fd95f9
4 changed files with 0 additions and 40 deletions
|
@ -7,5 +7,4 @@ CONFIG_BT_DIS_PNP=n
|
|||
CONFIG_BT_BAS=y
|
||||
CONFIG_BT_DEVICE_NAME="Zephyr Health Thermometer"
|
||||
CONFIG_BT_DEVICE_APPEARANCE=768
|
||||
CONFIG_BT_ATT_ENFORCE_FLOW=n
|
||||
CONFIG_CBPRINTF_FP_SUPPORT=y
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue