Felipe Moura 3c3afd04bd espressif/esp_pm.c: restore GPIO config after using it as a wake source ... Arming a pin as a light-sleep wake source destroyed whatever it was configured as, permanently. esp_pm_gpio_wakeup_prepare() has to reconfigure each masked pin to plain INPUT and hand it to gpio_wakeup_enable(), because the wakeup path only supports level triggering. It then never put anything back. A pin that was also a normal peripheral interrupt -- a sensor's data-ready line, say -- came out of the first light sleep with its trigger mode gone and never interrupted again. Nothing failed loudly; the device just went silent. Fixed generically rather than per-board: - esp_configgpio() now remembers the last attr applied to each pin, and a new esp_getconfiggpio() hands it back. This is what lets the PM code restore a pin without having to know what the pin is for. - esp_pm_gpio_wakeup_prepare() saves each masked pin's attr before overwriting it, and a new esp_pm_gpio_wakeup_restore() puts it back as soon as esp_pm_light_sleep_start() returns. Tied to the physical sleep/wake cycle deliberately, not to PM state transitions. An earlier attempt used a board-level pm_register()/notify() callback and never fired at all, because the board sits in PM_STANDBY without transitioning back to PM_NORMAL -- there is no state change to hang the restore on. The return from esp_pm_light_sleep_start() is the one event that always happens exactly once per sleep. Assisted-by: Claude:claude-opus-5 Signed-off-by: Felipe Moura <moura.fmo@gmail.com>		2026-09-23 08:36:17 -03:00
..
include	xtensa: Support BUILD_KERNEL.	2026-09-10 23:28:43 +08:00
src	espressif/esp_pm.c: restore GPIO config after using it as a wake source	2026-09-23 08:36:17 -03:00
CMakeLists.txt
Kconfig	arch/atomic: remove up_testset in spinlock	2026-09-08 08:58:54 +08:00