292aafef5a
According to RISC-V Instruction Set Manual Chapter 3.3.2: "The operation of WFI must be unaffected by the global interrupt bits in mstatus [...] WFI is also required to resume execution for locally enabled interrupts pending at any privilege level, regardless of the global interrupt enable at each privilege level." Disabling interrupts before executing `wfi` prevents a corner case where an IRQ is presented just before executing `wfi`, which would cause it to return directly into `wfi` and potentially get stuck in sleep, instead of continuing to background processing. When execution is resumed, interrupts are reenabled and appropriate IRQ Handlers should be executed. Signed-off-by: Marcin Szymczyk <marcin.szymczyk@nordicsemi.no>
23 lines
402 B
C
23 lines
402 B
C
/*
|
|
* Copyright (c) 2016 Jean-Paul Etienne <fractalclone@gmail.com>
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
#include <zephyr/irq.h>
|
|
#include <zephyr/tracing/tracing.h>
|
|
|
|
void __weak arch_cpu_idle(void)
|
|
{
|
|
sys_trace_idle();
|
|
__asm__ volatile("wfi");
|
|
irq_unlock(MSTATUS_IEN);
|
|
}
|
|
|
|
void __weak arch_cpu_atomic_idle(unsigned int key)
|
|
{
|
|
sys_trace_idle();
|
|
__asm__ volatile("wfi");
|
|
irq_unlock(key);
|
|
}
|