ea04fd95f9
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> |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| Kconfig | ||
| Kconfig.infineon | ||
| cyw43xxx.c | ||
| h4.c | ||
| h5.c | ||
| hci_b91.c | ||
| hci_esp32.c | ||
| hci_psoc6_bless.c | ||
| ipc.c | ||
| ipm_stm32wb.c | ||
| nrf53_support.c | ||
| slz_hci.c | ||
| spi.c | ||
| userchan.c | ||