-
Notifications
You must be signed in to change notification settings - Fork 3k
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 SFDP to blockdevice #13917
Move SFDP to blockdevice #13917
Conversation
@LDong-Arm, thank you for your changes. |
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.
+1 for the cleanup but this should be treated as a breaking change.
We already produced 6.5.0rc1 that includes f4b7f44#diff-490d1b3086e6701d59e391718c24ac8ed7d54c36490461ae9a6c22c8b6d3b6b2 . This partially reverts it? I wonder if this should be in rc2 or it goes in to the next release? |
What affects users is if they use BlockDevice, they need to ensure "blockdevice" is listed in "requires" in mbed_app.json. Is this enough to change the PR type to "major update"?
When will be RC2? If we still have some time, maybe we can review & merge this PR (should be a simple one) for RC2, then I'll update the CMake part in #13908 assuming it'll be in the next release? |
rc2 only if we find critical issue during testing now. If yes, please talk to @adbridge I assume this will be in the next release along with CMake updates to storage library. |
This is not a critical issue, so we can wait until the next release. |
That change did not have an impact as it removed an This new PR has an impact on bare metal since "blockdevice" is no longer listed in mbed_app.json. As Lingkai says, it will affect bare metal applications that use BlockDevice. |
Updated PR type and migration action in the description. |
CI started |
Jenkins CI Test : ❌ FAILEDBuild Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
Update BlockDevice dependency according to ARMmbed/mbed-os/pull/13917
Update BlockDevice dependency according to ARMmbed/mbed-os/pull/13917
CI failures:
|
This PR cannot be merged due to conflicts. Please rebase to resolve them. |
I've updated the PR to not remove |
CI started |
Jenkins CI Test : ❌ FAILEDBuild Number: 2 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
I need to move unit tests too |
Unit tests fixed |
Jenkins CI Test : ✔️ SUCCESSBuild Number: 3 | 🔒 Jenkins CI Job | 🌐 Logs & ArtifactsCLICK for Detailed Summary
|
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.
Now that SFDP is in blockdevice, why not device key? it's the last piece in the drivers.
SFDP is an internal utility so we are free to move it around, but DeviceKey is a public API and we don't want to introduce breaking changes. In my opinion, DeviceKey is also a kind of platform feature, and the best place for it is debatable. |
Summary of changes
As SFDP is only used by
[Q/O]SPIFBlockdevice
, it should really belong toblockdevice
.Having SFDP removed from
drivers
, there's no need to haveblockdevice
inbare-metal
anymore. But for compatibility with existing projects (e.g. mbed-bootloader), we don't do this clean up.Impact of changes
Bare metal does not depend on
blockdevice
anymore.Migration actions required
If a bare metal application uses
blockdevice
, it now needs to be listed in therequires
field ofmbed_app.json
- it's not provided bybaremetal
anymore.Documentation
None.
Pull request type
Test results
Reviewers
@ARMmbed/mbed-os-core