diff options
| author | Abhishek Pandit-Subedi <abhishekpandit@chromium.org> | 2020-07-07 10:28:44 -0700 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2020-07-14 19:19:04 +0200 |
| commit | a45aca510b73b745f27f39c6bb590b1743ea1792 (patch) | |
| tree | cb9d6f6ec4ebff93b539233971f420dc7f57ee2f /kernel/taskstats.c | |
| parent | 11ba468877bb23f28956a35e896356252d63c983 (diff) | |
| download | lwn-a45aca510b73b745f27f39c6bb590b1743ea1792.tar.gz lwn-a45aca510b73b745f27f39c6bb590b1743ea1792.zip | |
PM: sleep: core: Emit changed uevent on wakeup_sysfs_add/remove
Udev rules that depend on the power/wakeup attribute don't get triggered
correctly if device_set_wakeup_capable is called after the device is
created. This can happen for several reasons (driver sets wakeup after
device is created, wakeup is changed on parent device, etc) and it seems
reasonable to emit a changed event when adding or removing attributes on
the device.
Signed-off-by: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Reviewed-by: Stephen Boyd <swboyd@chromium.org>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'kernel/taskstats.c')
0 files changed, 0 insertions, 0 deletions