199fb21d52
Three bugfixes to the leds-gpio driver, plus minor whitespace tweaks: - Do the INIT_WORK() before registering each LED, so if its trigger becomes immediately active it can schedule work without oopsing.. - Use normal registration, not platform_driver_probe(), so that devices appearing "late" (hotplug type) can still be bound. - Mark the driver remove code as "__devexit", preventing oopses when the underlying device is removed. These issues came up when using this driver with some GPIO expanders living on serial busses, which act unlike "normal" platform devices: they can appear and vanish along with the serial bus driver. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Richard Purdie <rpurdie@rpsys.net> |
||
---|---|---|
.. | ||
Kconfig | ||
led-class.c | ||
led-core.c | ||
led-triggers.c | ||
leds-ams-delta.c | ||
leds-cm-x270.c | ||
leds-cobalt-qube.c | ||
leds-cobalt-raq.c | ||
leds-corgi.c | ||
leds-gpio.c | ||
leds-h1940.c | ||
leds-ixp4xx-gpio.c | ||
leds-locomo.c | ||
leds-net48xx.c | ||
leds-s3c24xx.c | ||
leds-spitz.c | ||
leds-tosa.c | ||
leds-wrap.c | ||
leds.h | ||
ledtrig-heartbeat.c | ||
ledtrig-ide-disk.c | ||
ledtrig-timer.c | ||
Makefile |