-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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.
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
Cancel incomplete BLE connection when CloseAllBleConnections() is called #27304
Cancel incomplete BLE connection when CloseAllBleConnections() is called #27304
Conversation
When CloseAllBleConnections() is called, any ongoing attempt to establish new BLE connection should be cancelled because it is no longer needed for a new BLE connection to establish. CancelConnection() of the connection delegate should be called to cancel any ongoing new BLE connection so that platform- specific BLEManager can do cleanup. This is needed because we are encountering a problem that BLEManager not doing clean up when establishing PASE session times out, causing problem in the BT layer. Since BLEManager is platform-specific, it doesn't have knowledge of when PASE times out. But BLEManager needs to do clean up whenever CloseAllBleConnections() is called.
PR #27304: Size comparison from a8a80bb to 7304b22 Increases (43 builds for bl602, bl702, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
Decreases (4 builds for psoc6)
Full report (46 builds for bl602, bl702, cc32xx, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
@cuizelin99 please sign the CLA |
@andy31415 What more do I need to do to sign CLA? I can find project-chip's CLA under my signed CLAs at https://cla-assistant.io/my-cla |
The licence/cla status says "waiting to be reported" so assuming it is hung somehow. Since you say you signed it/see it, I will bypass this check. Thank you for verifying! |
…) is called (project-chip#27304)" This reverts commit ad5403e. There are two issues: * project-chip#27607 which has had no response for weeks. * project-chip#28139 which breaks commissioning on Mac, and would break it on Linux if it implemented BLE connection cancellation. We need to sort out why CHIPDeviceController is canceling BLE connections when starting PASE over BLE (!).
…) is called (#27304)" (#28143) This reverts commit ad5403e. There are two issues: * #27607 which has had no response for weeks. * #28139 which breaks commissioning on Mac, and would break it on Linux if it implemented BLE connection cancellation. We need to sort out why CHIPDeviceController is canceling BLE connections when starting PASE over BLE (!).
@cuizelin99 Note: this PR was reverted to fix regressions. Please see #28143 (review) for a suggestion of what the PR maybe should have looked like instead. |
When CloseAllBleConnections() is called, any ongoing attempt to establish new BLE connection should be cancelled because it is no longer needed for a new BLE connection to establish. CancelConnection() of the connection delegate should be called to cancel any ongoing new BLE connection so that platform- specific BLEManager can do cleanup. This is needed because we are encountering a problem that BLEManager not doing clean up when establishing PASE session times out, causing problem in the BT layer. Since BLEManager is platform-specific, it doesn't have knowledge of when PASE times out. But BLEManager needs to do clean up whenever CloseAllBleConnections() is called.