mirror of
https://github.com/esphome/esphome.git
synced 2026-09-14 08:38:39 +00:00
J. Nick Koston
68442f0674
defines.h previously hardcoded ESPHOME_THREAD_MULTI_ATOMICS regardless of the active USE_<platform>, so the clang-tidy envs ended up compiling e.g. wake_esp8266.cpp with USE_ESP8266 + MULTI_ATOMICS both set — a combination that cannot occur in a real build and that mismatched the extern in wake.h. Pick the model that real codegen uses: USE_ESP8266 / USE_RP2040 / USE_NRF52 → SINGLE USE_BK72XX (ARMv5TE, no LDREX/STREX) → MULTI_NO_ATOMICS everything else (ESP32, host, RTL87XX, LN882X) → MULTI_ATOMICS With that, the single-only wake TUs (esp8266, rp2040, generic) can drop the defensive conditional and just define g_wake_requested as plain volatile again.
