- 04 Jan, 2016 40 commits
-
-
Ingi Kim authored
The refcount of device_node increases after of_node_get() is called. So, a break out of the loop requires of_node_put(). This patch adds missing of_node_put() when loop breaks. Signed-off-by:
Ingi Kim <ingi2.kim@samsung.com> Acked-by:
Rob Herring <robh@kernel.org> Signed-off-by:
Jacek Anaszewski <j.anaszewski@samsung.com>
-
Markus Hofstaetter authored
Some PWMs are disabled by default or the default pin setting does not match the LED_OFF state (e.g., active-low leds). Hence, the driver may end up reporting 0 brightness, but the leds are actually on using full brightness, because it never enforces its default configuration. So enforce it by calling led_pwm_set() after successfully registering the device. Tested on a Phytec phyFLEX i.MX6Q board based on kernel v3.19.5. Signed-off-by:
Markus Hofstaetter <markus.hofstaetter@ait.ac.at> Tested-by:
-
Uwe Kleine-König authored
The header of this file fixes the license to GPL 2 only without the option to use later version. So use the string "GPL v2" that is to be used in this case. Signed-off-by:
Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Acked-by:
Fabio Baltieri <fabio.baltieri@gmail.com> Signed-off-by:
-
Rob Herring authored
The transient trigger duration is documented to be in msec units, but is actually in jiffies units. Other time based triggers are in msec units as well. Fix the timer setup to convert from msec. This could break an existing userspace that worked around this problem, but exposing jiffies to userspace is just wrong and would break anyway if HZ is changed. Signed-off-by:
-
Jacek Anaszewski authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by: -
Jacek Anaszewski authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by: -
Jacek Anaszewski authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by: -
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
Andrew Lunn <andrew@lunn.ch> Signed-off-by:
Antonio Ospite <ao2@ao2.it> Reviewed-by:
Mark Brown <broonie@kernel.org>
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Work queues are not used in this driver, so remove the include. Signed-off-by: -
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
Dan Murphy <dmurphy@ti.com> Cc: Ricardo Ribalda <ricardo.ribalda@gmail.com>
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the driver, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the driver, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the driver, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the driver, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the driver, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the driver, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the driver, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the driver, and switch to using brightness_set_blocking op. Signed-off-by:
-
Andrew Lunn authored
Now the core implements the work queue, remove it from the driver, and switch to using brightness_set_blocking op. Signed-off-by:
-
Jacek Anaszewski authored
LED subsystem shifted responsibility for choosing between SYNC or ASYNC way of setting brightness from drivers to the caller. Adapt the wrapper to those changes. Signed-off-by:
Sakari Ailus <sakari.ailus@linux.intel.com> Acked-by:
Pavel Machek <pavel@ucw.cz> Acked-by:
Mauro Carvalho Chehab <mchehab@osg.samsung.com>
-
Jacek Anaszewski authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Jacek Anaszewski authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Jacek Anaszewski authored
Now the core implements the work queue, remove it from the drivers, and switch to using brightness_set_blocking op. Signed-off-by:
-
Jacek Anaszewski authored
This patch adds description of the LED subsystem API for setting an LED brightness. Signed-off-by:
-
Jacek Anaszewski authored
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 authored
This patch makes LED core capable of setting brightness for drivers that implement brightness_set_blocking op. It removes from LED class drivers responsibility for using work queues on their own. In order to achieve this set_brightness_delayed callback is being modified to directly call one of available ops for brightness setting. led_set_brightness_async() function didn't set brightness in an asynchronous way in all cases. It was mistakenly assuming that all LED subsystem drivers used work queue in their brightness_set op, whereas only half of them did that. Since it has no users now, it is being removed. Signed-off-by:
-
Jacek Anaszewski authored
This patch adds led_set_brightness_nosleep() and led_set_brightness_nopm() functions, that guarantee setting LED brightness in a non-blocking way. The latter is used from pm_ops context and doesn't modify the brightness cached in the struct led_classdev. Its execution always ends up with a call to brightness setting op - either directly or through a set_brightness_work, regardless of LED_SUSPENDED flag state. The patch also replaces led_set_brightness_async() with led_set_brightness_nosleep() in all places where the most vital was setting brightness in a non sleeping way but not necessarily asynchronously, which is not needed for non-blocking drivers. Signed-off-by:
-
Jacek Anaszewski authored
The initial purpose of brightness_set_sync op, introduced along with the LED flash class extension, was to add a means for setting torch LED brightness as soon as possible, which couldn't have been guaranteed by brightness_set op. This patch renames the op to brightness_set_blocking, which describes its purpose in a more generic way. It is beneficial in view of the prospective changes in the LED core, aiming at removing the need for using work queues in LED class drivers that can sleep or use delays while setting brightness. Signed-off-by:
-
Jacek Anaszewski authored
This patch adds LED_BLINK_BRIGHTNESS_CHANGE flag to indicate that blink brightness has changed, and LED_BLINK_DISABLE flag to indicate that blinking deactivation has been requested. In order to use the flags led_timer_function and set_brightness_delayed callbacks as well as led_set_brightness() function are being modified. The main goal of these modifications is to prepare set_brightness_work for extension of the scope of its responsibilities. Signed-off-by:
-
