From 5682a5ef365bc5bf7da3bcb555f94a418cd4e9a5 Mon Sep 17 00:00:00 2001 From: Jiang Jiang Jian Date: Wed, 13 Jun 2018 11:54:04 +0800 Subject: [PATCH] Merge branch 'bugfix/crosscore_handle_yield_iram' into 'master' esp32: Move esp_crosscore_isr_handle_yield() to IRAM See merge request idf/esp-idf!2544 (cherry picked from commit 8e7dfb230f4a607d353b82a173ca09170fb0b3fd) f6442abd esp32: Move esp_crosscore_isr_handle_yield() to IRAM --- components/esp32/crosscore_int.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/components/esp32/crosscore_int.c b/components/esp32/crosscore_int.c index 4a57a2b19..6e452faaf 100644 --- a/components/esp32/crosscore_int.c +++ b/components/esp32/crosscore_int.c @@ -44,7 +44,7 @@ static volatile uint32_t reason[ portNUM_PROCESSORS ]; ToDo: There is a small chance the CPU already has yielded when this ISR is serviced. In that case, it's running the intended task but the ISR will cause it to switch _away_ from it. portYIELD_FROM_ISR will probably just schedule the task again, but have to check that. */ -static void esp_crosscore_isr_handle_yield() +static inline void IRAM_ATTR esp_crosscore_isr_handle_yield() { portYIELD_FROM_ISR(); }