linux-kernel - [usbhid] identifying a particular usbhid device as wakeup reason?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Thu, 12 Oct 2017 17:38:55 -0700
From:   Rajat Jain <rajatja@...gle.com>
To:     linux-usb@...r.kernel.org, linux-input@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jiri Kosina <jikos@...nel.org>,
        Dmitry Torokhov <dtor@...gle.com>,
        "Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
        Linux PM <linux-pm@...r.kernel.org>
Subject: [usbhid] identifying a particular usbhid device as wakeup reason?

Hi usbhid folks,

I'd like to identify after a wakeup from suspend, that my USB HID
keyboard was used to wake up the system.

I'm trying to understand why don't I see "wakeup_count" increase for
my USB keyboard or trackpad in /sys/kernel/debug/wakeup_sources, when
I indeed woke up the system using the keyboard? I do not see
wakeup_count increased for any device (including the underlying usb
device for usbhid) when I wake using the keyboard.

I do see that the wakeup_count increases for other devices when I wake
using them (e.g. wifi on a PCI bus, or bluetooth controller on USB
bus).

My questions:

1) How can I go about fixing this problem?

2) Is it because the usbhid driver does not call pm_wakeup_event() on
wake? In retrospect, is it because the usbhid driver cannot tell that
its key presses indeed woke up the system (as opposite to if the
system was already up)?

Thanks,

Rajat