-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
drivers: bluetooth: hci: Simplify SPI driver #64453
drivers: bluetooth: hci: Simplify SPI driver #64453
Conversation
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.
Please split changes into logical commits (boards config update, LOG_HEX_DUMP
introduction, configure_cs
removal, ....)
Use LOG_HEXDUMP_DBG for SPI message logging instead of printk. Signed-off-by: Ali Hozhabri <[email protected]>
Remove redundant configure_cs as it is performed by SPI initialization. Signed-off-by: Ali Hozhabri <[email protected]>
7c74dbe
to
2ecca9e
Compare
2ecca9e
to
9830cb6
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.
2 minor comments, otherwise LGTM.
BLE maintainer approval required anyway
Modify SPI configuration to match the features introduced in PR zephyrproject-rtos#63437. Set the property "controller-data-delay-us" to zero for boards which are using BlueNRG-MS. Fix Chip Select configuration for stm32l562e_dk board. Signed-off-by: Ali Hozhabri <[email protected]>
9830cb6
to
54c31e1
Compare
STM32L562 Discovery kit is not compatible with Bluetooth over USB application. Add missing information related to the BLE capability of this board. Signed-off-by: Ali Hozhabri <[email protected]>
Replace hard-coded values with suitable macros. Signed-off-by: Ali Hozhabri <[email protected]>
54c31e1
to
37d7095
Compare
@@ -10,7 +10,7 @@ tests: | |||
- usb | |||
- bluetooth | |||
# FIXME: exclude due to build error | |||
platform_exclude: 96b_carbon | |||
platform_exclude: 96b_carbon stm32l562e_dk |
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.
Is this because of USB?
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.
Yes. Since the platform is running a 2-chip configuration where the controller part is running on BlueNRG-MS using an SPI interface, and the STM32L4xxxx is running the host part connected via SPI to the controller, therefore, the hci_usb protocol does not apply to this platform.
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.
LGTM :)
Used
LOG_HEXDUMP_DBG
for SPI message logging instead ofprintk
.Removed redundant
configure_cs
as it is performed by SPI initialization.Modified SPI configuration to match the features introduced in PR #63437.