-
Notifications
You must be signed in to change notification settings - Fork 7.4k
STM32: move dts.fixup files to soc level #5859
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
Conversation
dwagenk
commented
Jan 28, 2018
•
edited
Loading
edited
- move dts.fixup files contents from board level to soc family level for STM32 SOCs. (Move fixups definitions in .fixup files under dts/ #5707)
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.
Can you pull out the dts refactor’s into a separate PR. Those look good and happy to merge them right away.
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.
Seems like we should be able to get SPI loopback w/o having board specific conf files.
Codecov Report
@@ Coverage Diff @@
## master #5859 +/- ##
=======================================
Coverage 54.33% 54.33%
=======================================
Files 457 457
Lines 43298 43298
Branches 8302 8302
=======================================
Hits 23524 23524
Misses 19635 19635
Partials 139 139 Continue to review full report at Codecov.
|
This moves and merges the existing board-level dts.fixup files for STM32 F0 SOC family into one soc family level dts.fixup file. No new fixup blocks have been added, only fixup blocks, that were part of at least one board level dts.fixup file are present in soc family level dts.fixup file. Contributes to #5707 Signed-off-by: Daniel Wagenknecht <[email protected]>
This moves and merges the existing board-level dts.fixup files for STM32 F4 SOC family into one soc family level dts.fixup file. No new fixup blocks have been added, only fixup blocks, that were part of at least one board level dts.fixup file are present in soc family level dts.fixup file. 96b_carbon boards fixup block for Bluetooth HCI device via SPI stays in board level dts.fixup file, because it is board specific. Contributes to #5707 Signed-off-by: Daniel Wagenknecht <[email protected]>
This moves and merges the existing board-level dts.fixup files for STM32 F1 SOC family into one soc family level dts.fixup file. No new fixup blocks have been added, only fixup blocks, that were part of at least one board level dts.fixup file are present in soc family level dts.fixup file. Contributes to #5707 Signed-off-by: Daniel Wagenknecht <[email protected]>
This moves and merges the existing board-level dts.fixup files for STM32 F3 SOC family into one soc family level dts.fixup file. No new fixup blocks have been added, only fixup blocks, that were part of at least one board level dts.fixup file are present in soc family level dts.fixup file. Contributes to #5707 Signed-off-by: Daniel Wagenknecht <[email protected]>
This moves and merges the existing board-level dts.fixup files for STM32 L4 SOC family into one soc family level dts.fixup file. No new fixup blocks have been added, only fixup blocks, that were part of at least one board level dts.fixup file are present in soc family level dts.fixup file. disco_l475_iot1 boards fixup blocks for devices connected via SPI and I2C stay in board level dts.fixup file, because they are board specific. Contributes to #5707 Signed-off-by: Daniel Wagenknecht <[email protected]>
@ galak
changed this PR to only contain the dts refactor. |