-
Notifications
You must be signed in to change notification settings - Fork 8.1k
stm32wbax 802154 driver support #95376
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
stm32wbax 802154 driver support #95376
Conversation
The following west manifest projects have changed revision in this Pull Request:
Additional metadata changed:
⛔ DNM label due to: 1 project with metadata changes and 2 blob changes Note: This message is automatically posted and updated by the Manifest GitHub Action. |
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.
@vtardy-st, I have submitted a couple of comments, but I have realized that possibly a rebase is needed, before further review. Could you please rebase the code and re-submit?
f1be45e
to
9f01ddc
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.
Could you please explore the possibility of "merging" hci_if/ble and hci_if/IEEE802154 directories ? I think they perform similar functions.
021428a
to
a3f47ba
Compare
816cc3b
to
2b1fa83
Compare
114ce47
to
cbdc3c3
Compare
I'm not sure it's a good idea to have the manifest updated from its specific commit. At least the manifest update commit being after the commit enabling 802.15.4 on nucleo_wba65ri would also make that board to fail to build on that commit. Will earlier changes in the driver would make wba65 boards with BLE enabled to fail to build. I wonder if at least the commit that updates the manifest could be placed first in the series. |
Update hal_stm32 version to latest commit: dc7c2543a079c57a4e7dbee54ed7877880dc235b Signed-off-by: Vincent Tardy <[email protected]>
Add the driver itself and Kconfig/CMakeLists/dts/bindings related to it. Other files and libraries needed are in ST's dedicated folder hal_stm32 (modules/hal/stm32). Signed-off-by: Vincent Tardy <[email protected]>
Add ieee802154 driver in STM32 Wireless Platform section Signed-off-by: Vincent Tardy <[email protected]>
Add 802.15.4 support in hci_if files Signed-off-by: Vincent Tardy <[email protected]>
enable ieee802154 node for nucleo_wba65ri Signed-off-by: Vincent Tardy <[email protected]>
cbdc3c3
to
8f63660
Compare
|
@erwango - looks generally fine to me. @nashif and @MaureenHelm can comment on the MAINTAINERS file. |
Thanks @cfriedt. Do you know who has the final word on the |
Hi @vtardy-st! To celebrate this milestone and showcase your contribution, we'd love to award you the Zephyr Technical Contributor badge. If you're interested, please claim your badge by filling out this form: Claim Your Zephyr Badge. Thank you for your valuable input, and we look forward to seeing more of your contributions in the future! 🪁 |
Add support of 802.15.4 driver for STM32WBA
Update Kconfig/CMakeLists/dts/bindings related to 802.15.4 support for STM32WBA
In soc/stm32, update files to support of 802.15.4 on STM32WBA
Enable ieee802154 node for nucleo_wba65ri board