-
Notifications
You must be signed in to change notification settings - Fork 8.2k
kconfig: drivers: bluetooth: clean up Kconfig dependencies #14314
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
kconfig: drivers: bluetooth: clean up Kconfig dependencies #14314
Conversation
Remove use of select to "force" enabling other configs in subsys/fs and subsys/net/l2. The forcing will cause infinite kconfig recursion. Signed-off-by: Thomas Stenersen <[email protected]>
This moves the vendor-specific HCI command/event configuration definitions out of bluetooth/common into bluetooth. This allows the controller itself to indicate its support for vendor-specific commands/events. Signed-off-by: Thomas Stenersen <[email protected]>
Redefining the config will not let another (out-of-source) driver be chosen instead of the default. The driver is practically forced by the soc settings. This commit moves default settings from soc/arm/nordic_nrf into the drivers themselves. Signed-off-by: Thomas Stenersen <[email protected]>
Add choice variables for CLOCK_CONTROL_NRF_SOURCE and CLOCK_CONTROL_NRF_ACCURACY such that the choices may be augmented out-of-tree. Signed-off-by: Thomas Stenersen <[email protected]>
subsys/bluetooth/host/Kconfig
Outdated
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.
Why did you change the default here?
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.
To accommodate the worst case stack requirement if an out-of-tree controller is used. I'll add a comment in the code here and in the commit with the reasoning.
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 was ok with the previous PR, I'm also ok with this one :)
By specifying the controller directly when selecting the default BT_HCI_TX_STACK_SIZE, an external controller may rely on the final default value when none of the in-tree controllers are used. The value is increased to 1024 to accomodate the current worst-case stack size. Signed-off-by: Thomas Stenersen <[email protected]>
a150021 to
ab3a94e
Compare
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.
Re-approving
Codecov Report
@@ Coverage Diff @@
## master #14314 +/- ##
==========================================
+ Coverage 51.97% 52.12% +0.14%
==========================================
Files 308 308
Lines 45512 45527 +15
Branches 10546 10552 +6
==========================================
+ Hits 23656 23732 +76
+ Misses 17055 16990 -65
- Partials 4801 4805 +4
Continue to review full report at Codecov.
|
|
Merging since this is the non-contentious portion of #13631 which was already reviewed several days ago. |
These are the changes from #13631 without the out-of-tree driver support. It cleans up Kconfig dependencies in Nordic drivers and in the Bluetooth subsystem.