diff options
| author | Stephen Boyd <swboyd@chromium.org> | 2019-08-19 15:41:57 -0700 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2019-08-21 00:25:16 +0200 |
| commit | 2ca3d1ecb8c432ee212d80fa7615cdd5d1df62e3 (patch) | |
| tree | 89b3ae2a339df6e794c3f7efef474a3e089e8185 /kernel/stackleak.c | |
| parent | ae367b7936408444afc76a8a3e141abede9ccbe4 (diff) | |
| download | linux-2ca3d1ecb8c432ee212d80fa7615cdd5d1df62e3.tar.bz2 | |
PM / wakeup: Register wakeup class kobj after device is added
The device_set_wakeup_enable() function can be called on a device that
hasn't been registered with device_add() yet. This allows the device to
be in a state where wakeup is enabled for it but the device isn't
published to userspace in sysfs yet.
After commit c8377adfa781 ("PM / wakeup: Show wakeup sources stats in
sysfs"), calling device_set_wakeup_enable() will fail for a device that
hasn't been registered with the driver core via device_add(). This is
because we try to create sysfs entries for the device and associate a
wakeup class kobject with it before the device has been registered.
Let's follow a similar approach that device_set_wakeup_capable() takes
here and register the wakeup class either from
device_set_wakeup_enable() when the device is already registered, or
from dpm_sysfs_add() when the device is being registered with the driver
core via device_add().
Fixes: c8377adfa781 ("PM / wakeup: Show wakeup sources stats in sysfs")
Reported-by: Qian Cai <cai@lca.pw>
Reviewed-by: Tri Vo <trong@android.com>
Signed-off-by: Stephen Boyd <swboyd@chromium.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'kernel/stackleak.c')
0 files changed, 0 insertions, 0 deletions