Display driver suspend API improvement#7006
Conversation
Remove `bool touch_wakeup_enabled` from `display_suspend()` and `display_resume()`. The parameter was too specific to touch-panel hardware and leaked touch wakeup policy into the display driver. The branching between light-suspend and full deinit is moved to `suspend_io.c`, which is the appropriate level of abstraction. `display_resume()` now handles both cases internally: light-resume when the driver is still initialized, and full reinit when it was fully deinitialized during suspend. [no changelog]
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughThis PR simplifies the display suspend/resume API by removing a Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
| model | device_test | click_test | persistence_test |
|---|---|---|---|
| T2T1 | test(all) main(all) ![]() |
test(all) main(all) ![]() |
test(all) main(all) ![]() |
| T3B1 | test(all) main(all) ![]() |
test(all) main(all) ![]() |
test(all) main(all) ![]() |
| T3T1 | test(all) main(all) ![]() |
test(all) main(all) ![]() |
test(all) main(all) ![]() |
| T3W1 | test(all) main(all) ![]() |
test(all) main(all) ![]() |
test(all) main(all) ![]() |
Latest CI run: 26511661689




































Remove
bool touch_wakeup_enabledparameter fromdisplay_suspend()anddisplay_resume()— it was too specific to touch-panel hardware and leaked touch wakeup policy into the display driver.Move the branching logic (light-suspend vs. full deinit) up to
suspend_io.c, which is the appropriate level of abstraction.display_resume()now handles both cases internally: light-resume when the driver is still initialized, and full reinit when it was fully deinitialized during suspend.