-
Notifications
You must be signed in to change notification settings - Fork 7.9k
move IronSide APIs from drivers/firmware to soc/nordic #91910
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
move IronSide APIs from drivers/firmware to soc/nordic #91910
Conversation
2ac6b57
to
53667e7
Compare
86f4440
to
ab17f0c
Compare
@57300 is the 4.2 milestone here intentional? IE do you want this to be merged in before the RC2 as a "cosmetic change"? |
s/IRONside/IronSide/g Signed-off-by: Grzegorz Swiderski <[email protected]>
Move the IronSide APIs to soc/nordic from drivers/firmware since these are vendor specific APIs. The header files are now included from <nrf_ironside/*.h>. Adjust code that uses these APIs accordingly. Also move the DT binding for "nordic,ironside-call" from bindings/firmware to bindings/misc. Signed-off-by: Jonathan Nilsen <[email protected]>
Use designated IRQ numbers, instead of generic defaults. Signed-off-by: Grzegorz Swiderski <[email protected]>
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.
Rebased to fix conflicts.
@danieldegrasse Yes, these are cosmetic changes we would like to get in for v4.2.0, because it will be the first Zephyr release with support for IronSide. Moving the API is also a part of resolving #91373.
|
Move the IronSide APIs to soc/nordic from drivers/firmware since these are vendor specific APIs.
The header files are now included from <nrf_ironside/*.h>.
Adjust code that uses these APIs accordingly.
Also move the DT binding for "nordic,ironside-call" from bindings/firmware to bindings/misc.
Also includes a commit with some minor spelling adjustments before the move.