-
Notifications
You must be signed in to change notification settings - Fork 31
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
Initialize the FRB2 watchdog timer in DXE phase if PEI is not supported. #257
Conversation
Initialize the FRB2 watchdog timer in DXE phase if PEI is not supported.
@microsoft-github-policy-service agree company="Microsoft" |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #257 +/- ##
==========================================
- Coverage 28.32% 28.20% -0.13%
==========================================
Files 44 44
Lines 2990 3003 +13
Branches 404 404
==========================================
Hits 847 847
- Misses 2131 2144 +13
Partials 12 12
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Initialize the FRB2 watchdog timer in DXE phase if PEI is not supported.
Description
PEIM driver support was limited on ARM based project and caused FRB2
watchdog timer was not enabled.
Expected Behavior:
FRB2 watchdog timer should be set correctly based on policy.
FIX APPLIED:
Add FRB2 timer running check, if timer is not running and policy is set,
enable FRB2 watchdog timer.
For details on how to complete these options and their meaning refer to CONTRIBUTING.md.
How This Was Tested
Tested with ARM based project and observed the watchdog timer was set
based on policy setting.
Integration Instructions
N/A