You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a few boards that support deep sleep and have a display, but the display becomes unusable after fake deep sleep, because the display is not released prior to being re-inited on wake. The FunHouse does release displays in board_deinit() and doesn't have the issue.
Should that be added to all relevant board.c ? Or should a call to release displays be added to the fake sleep code in main.c ? After board_deinit() for example. Some boards with an e-ink display have their own thing where they wait for the display to finish refreshing before releasing.
Example boards that need the fix that I could test:
adafruit_feather_esp32s2_tft
hiibot_iots2
lilygo_ttgo_t8_s2_st7789
adafruit_macropad_rp2040
The text was updated successfully, but these errors were encountered:
There are a few boards that support deep sleep and have a display, but the display becomes unusable after fake deep sleep, because the display is not released prior to being re-inited on wake. The FunHouse does release displays in board_deinit() and doesn't have the issue.
Should that be added to all relevant
board.c
? Or should a call to release displays be added to the fake sleep code in main.c ? After board_deinit() for example. Some boards with an e-ink display have their own thing where they wait for the display to finish refreshing before releasing.Example boards that need the fix that I could test:
The text was updated successfully, but these errors were encountered: