linux-toradex.git/drivers/leds, branch v2.6.33.5

leds-gpio: fix default state handling on OF platforms

2010-04-01T23:01:58+00:00

commit 0493a4ff10959ff4c8e0d65efee25b7ffd4fa5db upstream.

The driver wrongly sets default state for LEDs that don't specify
default-state property.

Currently the driver handles default state this way:

memset(&led, 0, sizeof(led));
for_each_child_of_node(np, child) {
	state = of_get_property(child, "default-state", NULL);
	if (state) {
		if (!strcmp(state, "keep"))
			led.default_state = LEDS_GPIO_DEFSTATE_KEEP;
		...
	}
	ret = create_gpio_led(&led, ...);
}

Which means that all LEDs that do not specify default-state will inherit
the last value of the default-state property, which is wrong.

This patch fixes the issue by moving LED's template initialization into
the loop body.

Signed-off-by: Anton Vorontsov 
Signed-off-by: Andrew Morton 
Signed-off-by: Richard Purdie 
Signed-off-by: Greg Kroah-Hartman

leds: leds-pwm: Set led_classdev max_brightness

2009-12-17T11:42:34+00:00

Currently the driver leds-pwm doesn't set max_brightness for the led device
although it's platform data proides a maximum brightness. Instead it stores its
own private driver struct. The max_brightness defaults to 255 for led device if
it has not been set.
As a result any leds-pwm device with a different maximum brightness will show
incorrect behavior, as it is posible to either set a longer then period duty
time or not be able to switch the led to full brightness.

Signed-off-by: Lars-Peter Clausen 
Signed-off-by: Richard Purdie

leds: use default-on trigger for Cobalt Qube

2009-12-17T11:38:31+00:00

This patch changes the default trigger from "ide-disk"
to "default-on". Users updating from kernels not having this
LED driver will prefer having the same LED behavior as they
used to.

Signed-off-by: Florian Fainelli 
Signed-off-by: Richard Purdie

leds: drivers/leds/leds-ss4200.c: fix return statement

2009-12-17T11:36:40+00:00

drivers/leds/leds-ss4200.c: In function 'ich7_lpc_probe':
drivers/leds/leds-ss4200.c:353: warning: 'return' with no value, in function returning non-void

Signed-off-by: Andrew Morton 
Signed-off-by: Richard Purdie

leds: Add LED class driver for regulator driven LEDs.

2009-12-17T11:27:09+00:00

This driver provides an interface for controlling LEDs (or vibrators)
connected to PMICs for which there is a regulator framework driver.

This driver can be used, for instance, to control vibrator on all Motorola EZX
phones using the pcap-regulator driver services.

Signed-off-by: Antonio Ospite 
Reviewed-by: Mark Brown 
Signed-off-by: Richard Purdie

leds: leds-cobalt-qube.c: use resource_size()

2009-12-17T11:18:15+00:00

Use resource_size() for ioremap.

Signed-off-by: H Hartley Sweeten 
Signed-off-by: Richard Purdie

leds: leds-cobalt-raq.c - use resource_size()

2009-12-17T11:16:23+00:00

Use resource_size() for ioremap.

Signed-off-by: H Hartley Sweeten 
Signed-off-by: Richard Purdie

leds: Add driver for ADP5520/ADP5501 MFD PMICs

2009-12-16T11:30:10+00:00

Signed-off-by: Michael Hennerich 
Signed-off-by: Bryan Wu 
Signed-off-by: Mike Frysinger 
Signed-off-by: Richard Purdie

leds: Add driver for LT3593 controlled LEDs

2009-12-16T11:30:09+00:00

The LT3593 is a step-up DC/DC converter designed to drive up to ten
white LEDs in series. The current flow can be set with a control pin.

This driver controls any number of such devices connected on generic
GPIOs and exports the function as as platform_driver.

The gpio_led platform data struct definition is reused for this purpose.

Successfully tested on a PXA embedded board.

Signed-off-by: Daniel Mack 
Signed-off-by: Richard Purdie

leds-ss4200: Check pci_enable_device return

2009-12-16T11:30:09+00:00

pci_enable_result is defined using the __must_check macro but
leds-ss4200 is not checking the return value.

Signed-off-by: Javier Martinez Canillas 
Signed-off-by: Dave Hansen 
Signed-off-by: Richard Purdie