summaryrefslogtreecommitdiffstats
path: root/drivers/input/serio/serio.c
diff options
context:
space:
mode:
authorStephen Boyd <swboyd@chromium.org>2019-08-29 14:31:05 -0700
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2019-08-29 14:42:11 -0700
commitc8a144b250dcd5fe6df95b8d101e9e2fe4c16201 (patch)
tree69eca6a8bf2d3e9cc1f7a739ab5d7da6135e3a12 /drivers/input/serio/serio.c
parent53119e513478b3b5c2b81a9a049f52cf17fcfff3 (diff)
downloadlinux-c8a144b250dcd5fe6df95b8d101e9e2fe4c16201.tar.bz2
Input: i8042 - enable wakeup on a stable struct device
We don't know when the device will be added with device_add() in serio_add_port() because serio_add_port() is called from a workqueue that this driver schedules by calling serio_register_port(). The best we can know is that the device will definitely not have been added yet when the start callback is called on the serio device. While it hasn't been shown to be a problem, proactively move the wakeup enabling calls to the start hook so that we don't race with the workqueue calling device_add(). This will avoid racy situations where code tries to add wakeup sysfs attributes for this device from dpm_sysfs_add() but the path in device_set_wakeup_capable() has already done so. Signed-off-by: Stephen Boyd <swboyd@chromium.org> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'drivers/input/serio/serio.c')
0 files changed, 0 insertions, 0 deletions