From 249d1bcc3b2f262712fe882adeb37f38c932ec08 Mon Sep 17 00:00:00 2001 From: "J. Nick Koston" Date: Mon, 28 Jul 2025 22:11:27 -1000 Subject: [PATCH] Update esphome/components/esp32_touch/esp32_touch_v1.cpp Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- esphome/components/esp32_touch/esp32_touch_v1.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/esphome/components/esp32_touch/esp32_touch_v1.cpp b/esphome/components/esp32_touch/esp32_touch_v1.cpp index d41f1615c8..ffb805e008 100644 --- a/esphome/components/esp32_touch/esp32_touch_v1.cpp +++ b/esphome/components/esp32_touch/esp32_touch_v1.cpp @@ -202,7 +202,7 @@ void IRAM_ATTR ESP32TouchComponent::touch_isr_handler(void *arg) { // Read current value using ISR-safe API // IMPORTANT: ESP-IDF v5.4 regression - touch_pad_read_filtered() is no longer ISR-safe - // In v5.3 and earlier it was ISR-safe, but v5.4 added mutex protection that causes: + // In ESP-IDF v5.3 and earlier it was ISR-safe, but ESP-IDF v5.4 added mutex protection that causes: // "assert failed: xQueueSemaphoreTake queue.c:1718" // We must use raw values even when filter is enabled as a workaround. // Users should adjust thresholds to compensate for the lack of IIR filtering.