-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[v2.6.4-NCSDK-34113-branch] Bluetooth: nRF Connect SDK v2.6.4 NCSIDB-1718 cherry-picks #24800
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
Merged
carlescufi
merged 12 commits into
nrfconnect:v2.6.4-NCSDK-34113-branch
from
cvinayak:github_ncs_v2_6_4_branch_NCSIDB-1718
Oct 24, 2025
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
a7157e7
bluetooth: controller: hci_driver: Add option to enable power class 1
sean-madigan 84eceb5
bluetooth: controller: add k_panic() if the hci packet is too big
olivier-le-sage e6bd215
bluetooth: hci_driver: Fix deadlock in MPSL workq
PavelVPV 13bb626
bluetooth: hci_driver: Process recvd msgs directly from SDC callback
PavelVPV f7897b5
Bluetooth: Controller: Ensure controller can handle flow control buffers
KyraLengfeld d596e47
Bluetooth: Controller: Disable new unit test missing framework
cvinayak 4b11391
Bluetooth: Controller: Port HCI Command buffer allocation
cvinayak b498533
bluetooth: controller: add missing feature bit for power class 1
thomas-m-johansen 390e553
Samples: Bluetooth: Explicitly set CONFIG_BT_BUF_EVT_RX_COUNT
weeTike 61fbe37
test-manifest: Update to reference ncs-v2.6-branch-NCSDK-34113-2-prev…
cvinayak 82a2504
manifest: Update zephyr, sidewalk, nrfxlib and dragoon for NCSIDB-1718
cvinayak 858c259
version: Update to 2.6.4-NCSDK-34113-2-preview1
cvinayak File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1 @@ | ||
| 2.6.4 | ||
| 2.6.4-NCSDK-34113-2-preview1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -15,3 +15,6 @@ CONFIG_SERIAL=y | |
| CONFIG_CONSOLE=y | ||
|
|
||
| CONFIG_BOOTLOADER_MCUBOOT=y | ||
|
|
||
| # BT | ||
| CONFIG_BT_BUF_CMD_TX_COUNT=3 | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess that your intention here is to reduce RAM usage next to setting
CONFIG_BT_BUF_EVT_RX_COUNT=4(to prevent RAM overflows). I am slightly worried that the extra configuration changes added here might introduce edge cases.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
E.g. IIRC
CONFIG_BT_CONN_TX_MAXused value of4here to allow transmitting:2 * GATT notification with HID mouse input report (required for motion data pipeline)
1 * GATT notification with battery data (BAS)
1 * GATT read response
Setting it to the value of
3might not cover all of the edge cases.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updates in dongle's configuration might require additional testing too
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The RAM overflows seem small:
Still, I do not see a simple change that could allow us to reduce the memory usage here. This might require further investigation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see support for 52810 was dropped here: f66256c
Is this a concern for the v2.6.4-x? this is a preview tag.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think customers are likely to use the preview tag with the updated nRF Desktop devices? If so, then they might possibly reveal some edge cases.
Still I am not sure if it's mandatory to support these 2 devices from this particular tag (I think this would need to be consulted with PMT).