#358 - Improved reset framework - #359
Open
vintagepc wants to merge 8 commits into
Open
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #359 +/- ##
==========================================
+ Coverage 91.45% 91.48% +0.02%
==========================================
Files 167 167
Lines 7793 7818 +25
==========================================
+ Hits 7127 7152 +25
Misses 666 666 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
vintagepc
marked this pull request as ready for review
March 11, 2022 14:00
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.
Description
Fixes resets not properly resetting peripherals and gives them a chance to (re)set their GPIO states.
Behaviour/ Breaking changes
Quite an invasive change, likely to break a few things where the current behaviour happens to work but is not technically correct....
Linked issues: