-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Nrfx 8402 run power consumption in idle cache retained #24761
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
Nrfx 8402 run power consumption in idle cache retained #24761
Conversation
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 0e2cee3f3b4989ecbf81cc588e6ecd7d112fe65d more detailssdk-nrf:
Github labels
List of changed files detected by CI (17)
Outputs:ToolchainVersion: f66cf421f3 Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
You can find the documentation preview for this PR here. |
7e19251
to
576338d
Compare
576338d
to
cca170c
Compare
cca170c
to
84910af
Compare
4e48b35
to
89a27cf
Compare
d93ef41
to
f5ff4b3
Compare
Works in CI
|
Extend tests with configuration that checks driver operation together with Low Power CPU state IDLE with cache retained. Signed-off-by: Sebastian Głąb <[email protected]>
Recently, there were improvements in the idle_ppr test. Apply similar changes to the idle_flpr test. Since, FLPR doesn't support GPIO, skip code that indicates cpu activity. Signed-off-by: Sebastian Głąb <[email protected]>
Pytest requires the first captured state to be low power state. Due to internal test framework delays, Pytest collects last ~27 ms of the idle state. Then MCU wakes up. As a result some Idle tests started to randomly fail. Add arbitrary delay at the beginning of main so the first wake up happens later. Signed-off-by: Sebastian Głąb <[email protected]>
f5ff4b3
to
0e2cee3
Compare
No description provided.