Fix wakeup count issue for the AT2 keyboard driver |
||
Issue descriptionAs part of enabling dark resume on Chromebooks again, we need to identify the wake source. We depend on wakeup_count of input devices to identify the device that woke the system up. As a fall back, we also look at events from input devices. If we see an input event when in dark resume, we do a full resume. But currently on devices that use AT keyboard driver, neither wakeup_count nor input events are reported when a wake is caused by key press. This is the tracking bug to fix the same.
,
Jun 1 2018
sent a patch upstream for the same. https://www.spinics.net/lists/linux-input/msg56612.html
,
Jan 18
(4 days ago)
De-prioritizing to '3' given 'available' status & removing milestones accordingly. If you disagree please mark 'untriaged'. |
||
►
Sign in to add a comment |
||
Comment 1 by ravisadineni@chromium.org
, May 30 2018