Hi, On Tue, Jan 9, 2024 at 11:31 PM Kai-Heng Feng <kai.heng.feng@xxxxxxxxxxxxx> wrote: > > > I'd also note that I'm really not sure what ChromeOS dark resume has > > to do with anything here. Dark resume is used for certain types of > > events that wakeup the system where we can identify that the event > > shouldn't turn the screen on, then we do some processing, then we go > > back to sleep. I'm nearly certain that a trackpad / touchscreen wakeup > > event would never qualify for "dark resume". If we see a > > trackpad/touchscreen event then we'll wakeup the system. If the system > > is in a state where trackpad/touchscreen events shouldn't wake us up > > then we disable those wakeups before going to suspend... > > Doesn't Dark Resume use wakeup count to decide whether the system > should wake up or go back to suspend? > For this case the input report is empty, hence wakeup count remains > the same after the wakeup. I assumed Dark Resume will check the wakeup > count and decide to put the system back to suspend. Ah, I understand now. So you're saying that the issue wouldn't be so bad (or maybe we wouldn't notice it) on systems with dark resume. However, even with dark resume we're not in a super great shape. Doing a dark resume isn't exactly a lightweight operation, since it can take a bit of time to resume the system, realize that there were no wakeup events, and then go back to sleep. I'm not a total expert on dark resume, but I believe that even with dark resume, there may also be artifacts that a user might notice (like perhaps USB devices powering up or perhaps the suspend LED on the system showing that we're not in suspend anymore). > > It seems to me like the board you're testing on has some strange bug > > and that bug should be fixed, or (in the worst case) you should send a > > patch to detect this broken touchpad and disable wakeup for it. > > It's desired to keep the wakeup capability, disabling wakeup isn't ideal here. > I'll write a patch to use touchpad specific quirk instead of applying > the change universally. Thanks! I'd also be curious if this is a problem for everyone with the Cirque touchpad or if it's board-specific. I could imagine the behavior you describe as coming about due to a missing or misconfigured pull resistor on the IRQ line. ...or perhaps a pull resistor pulling up to the wrong voltage rail... -Doug
