cpu/cortexm: move CPU_ARCH/FAM to Makefile.features#13392
Merged
aabadie merged 1 commit intoRIOT-OS:masterfrom Feb 18, 2020
Merged
cpu/cortexm: move CPU_ARCH/FAM to Makefile.features#13392aabadie merged 1 commit intoRIOT-OS:masterfrom
aabadie merged 1 commit intoRIOT-OS:masterfrom
Conversation
benpicco
approved these changes
Feb 17, 2020
Contributor
benpicco
left a comment
There was a problem hiding this comment.
Murdock is happy and this just moves code around.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contribution description
This PR moves CPU_ARCH/CPU_FAM variables defined for cortexm CPUs from Makefile.include to Makefile.features.
This allows for determining earlier if some CortexM sub-architectures provides low-level features, such FPU or MPU.
The efm32 were already updated this way in #13174.
The kinetis family is not adapted yet because it needs more work. This can be done in follow-up PRs.
Testing procedure
Issues/PRs references
Required by ##13391 and #13236. Also related to #9913.