summaryrefslogtreecommitdiff
path: root/drivers/leds/led-class-flash.c
diff options
context:
space:
mode:
authorJacek Anaszewski <j.anaszewski@samsung.com>2015-10-07 12:10:43 +0300
committerJacek Anaszewski <j.anaszewski@samsung.com>2016-01-04 11:57:31 +0300
commit13ae79bbe4c214047f51623304d83b46eb02897d (patch)
tree8dcbaf1fef57d97dfe78a35f07a84a8b85180122 /drivers/leds/led-class-flash.c
parent1afcadfcd184c3b52e38bae15c247a5fa4a0e054 (diff)
downloadlinux-13ae79bbe4c214047f51623304d83b46eb02897d.tar.xz
leds: core: Drivers shouldn't enforce SYNC/ASYNC brightness setting
This patch removes SET_BRIGHTNESS_ASYNC and SET_BRIGHTNESS_SYNC flags. led_set_brightness() now calls led_set_brightness_nosleep() instead of choosing between sync and async op basing on the flags defined by the driver. From now on, if a user wants to make sure that brightness will be set synchronously, they have to use led_set_brightness_sync() API. It is now being made publicly available since it has become apparent that it is a caller who should decide whether brightness is to be set in a synchronous or an asynchronous way. Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com> Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Diffstat (limited to 'drivers/leds/led-class-flash.c')
-rw-r--r--drivers/leds/led-class-flash.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/drivers/leds/led-class-flash.c b/drivers/leds/led-class-flash.c
index 300a2c9007ca..f53783b8d5e8 100644
--- a/drivers/leds/led-class-flash.c
+++ b/drivers/leds/led-class-flash.c
@@ -316,10 +316,6 @@ int led_classdev_flash_register(struct device *parent,
if (ret < 0)
return ret;
- /* Setting a torch brightness needs to have immediate effect */
- led_cdev->flags &= ~SET_BRIGHTNESS_ASYNC;
- led_cdev->flags |= SET_BRIGHTNESS_SYNC;
-
return 0;
}
EXPORT_SYMBOL_GPL(led_classdev_flash_register);