Skip to content

nimble/host: L2CAP fallback for LL conn param rejection #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gmarull wants to merge 1 commit into from
Closed

nimble/host: L2CAP fallback for LL conn param rejection #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions nimble/host/src/ble_gap.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6347,6 +6347,19 @@ ble_gap_update_params(uint16_t conn_handle,
rc = 0;
} else {
rc = ble_gap_update_tx(conn_handle, params);

/*
* If the controller rejects the LL update with "Unsupported Remote
* Feature" and we are the slave, fall back to L2CAP signaling. This
* can happen when the peer advertises CONN_PARAM_REQUEST support at
* the host level but the local controller does not support the 4.1 LL
* Connection Parameters Request procedure.
*/
if (rc == BLE_HS_HCI_ERR(BLE_ERR_UNSUPP_REM_FEATURE) &&
!(conn->bhc_flags & BLE_HS_CONN_F_MASTER)) {
l2cap_update = 1;
rc = 0;
}
}

done:
Expand Down
Loading