On Tue, Jun 13, 2017 at 12:50 AM, Jérôme de Bretagne <jerome.debretagne@xxxxxxxxx> wrote: >>> That was my assumption also, since my earlier 3-liner patch was doing >>> this exactly: trying to wake up on a regular 0xCE event. And it did work. >> >> OK >> >> Can you try the patch below, please? > > Thank you for this patch proposal. I've applied it but the system with > BIOS 1.1.31 doesn't wake up on short press. > > I can see the following (added) messages in the logs for info: > > - short press first while suspended -> no wake-up > [ 702.567912] intel-hid INT33D5:00: notify_handler with event 0xce > [ 702.567913] intel-hid INT33D5:00: 0xce == 0xc0 || !priv->array > [ 702.765067] intel-hid INT33D5:00: notify_handler with event 0xcf > [ 702.765072] intel-hid INT33D5:00: 0xcf == 0xc0 || !priv->array > - long press then -> waking up the system > [ 704.954703] intel-hid INT33D5:00: notify_handler with event 0xce > [ 704.954704] intel-hid INT33D5:00: 0xce == 0xc0 || !priv->array > [ 711.646088] intel-hid INT33D5:00: notify_handler with event 0xcf > [ 711.646092] intel-hid INT33D5:00: unknown event 0xcf > > confirming that priv->array is indeed not set, even with the patch below. > > With BIOS 1.1.20, I don't have such logs, notify_handler seems never called. OK I've just had a look at the acpidump output files you attached to https://bugzilla.kernel.org/show_bug.cgi?id=195897 and actually none of them has anything like BTNC or BTNE or similar under the device object intel-hid binds to. In fact, the definition of that device object on both the BIOS versions is exactly the same AFAICS. However, BIOS 1.1.31 contains additional Notify () invocations in the NEVT () method used for processing EC events (invoked by _Q66) with event values corresponding to the 5-button array power button scancodes. That's why your first debug patch works. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
