AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 13 Bitcoin

feat(core): touch wake-up feature introduction

Public commit record

What the developer wrote

Authored by bleska

92/100 · Strong
feat(core): touch wake-up feature introduction

It enables waking the T3W1 device up by display touch from suspend mode:
- Adding display suspend/resume functionality because, until now, the display driver has controlled the PWREN MOSFET and RESET signals, which are shared with the touch driver logic.
- Since it's not possible to switch the display off, it's put into deep standby mode, from which only an external HW reset can wake it up.
- The touch controller is being used in "monitor" mode, which can detect a touch event and generate an INT signal to wake the MCU. Once touched, the controller switches to active mode.
- Adding the "TOUCH_WAKEUP_ENABLED" macro and preprocessor-based conditional compilation for controlling whether this feature is enabled/disabled in the build (it's preparation for "checkbox"-based enabling/disabling control).

[no changelog]
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
The short version

What changed, and why it matters

This commit adds a new hardware feature for the Trezor T3W1 device that lets the user wake the device from suspend mode by touching the screen. It changes how the display and touch drivers are turned off and back on, and adds a new wake-up flag for touch events. The feature is currently disabled by default in the build configuration (TOUCH_WAKEUP_ENABLED is set to 0). There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a normal feature addition.

Recommended action

Treat as a feature commit rather than a security patch. If reviewing for security, verify that the new EXTI interrupt handler cannot be triggered spuriously to wake the device unexpectedly, that touch controller monitor mode re-entry timing does not introduce race conditions, and that the panel_suspend TODOs are completed before the feature is enabled. No immediate security action is indicated by the commit content alone.

Security signals we found

01

New interrupt-driven wake-up path added to touch driver

02

Display suspend/resume logic refactored with shared power/reset lines between display and touch controllers

03

Touch controller placed in monitor mode during suspend with automatic re-entry after 1 second

04

TODO stubs for panel_suspend on two of three panel variants (lx200d2406a and stm32u5a9j-dk) return false

05

Feature is disabled by default via TOUCH_WAKEUP_ENABLED=0 in build configs

Risk score

Why this scored 13/100

Our methodology →
Potential impact 2/30
Exploitability 2/25
Stealth signal 1/15
Affected reach 3/15
Confidence 3/10
Evidence quality 2/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.