config: handle device change event properly
wakeup_handler in udev.c wasn't dealing with udev change events. There are situations when a device can gain its input capabilities after it has been added to the system and therefore the change events must be handled as well. The change is handled as a consecutive device removal and addition. Signed-off-by: Erkki Seppälä <erkki.seppala@vincit.fi> Signed-off-by: Stefan Kost <Stefan.Kost@nokia.com> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
parent
fad10cb38e
commit
6243332782
|
@ -255,6 +255,10 @@ wakeup_handler(pointer data, int err, pointer read_mask)
|
||||||
device_added(udev_device);
|
device_added(udev_device);
|
||||||
else if (!strcmp(action, "remove"))
|
else if (!strcmp(action, "remove"))
|
||||||
device_removed(udev_device);
|
device_removed(udev_device);
|
||||||
|
else if (!strcmp(action, "change")) {
|
||||||
|
device_removed(udev_device);
|
||||||
|
device_added(udev_device);
|
||||||
|
}
|
||||||
}
|
}
|
||||||
udev_device_unref(udev_device);
|
udev_device_unref(udev_device);
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue
Block a user