linux-toradex.git/drivers/leds, branch imx-android-r12

Merge remote branch 'android/android-2.6.38' into imx_2.6.38

2011-07-26T05:26:08+00:00

Conflicts:
	drivers/misc/Kconfig
	drivers/misc/Makefile
	drivers/net/wireless/Makefile
	include/linux/mmc/mmc.h
	kernel/power/main.c

ENGR00141391-2 PMIC: porting da9053 to i.mx platform

2011-04-01T03:34:09+00:00

Fix da9053 backlight Kconfig error
porting da9052 regulator driver

Signed-off-by: Zhou Jingyu 
Acked-by: Lily Zhang

ENGR00141391-1 PMIC: Add DA9053 source code from Dialog

2011-04-01T03:34:07+00:00

Add DA9053 original source code

Signed-off-by: Zhou Jingyu 
Acked-by: Lily Zhang

ledtrig-sleep: Add led trigger for sleep debugging.

2011-03-29T20:57:35+00:00

Signed-off-by: Brian Swetland

leds: leds-pwm: return proper error if pwm_request failed

2011-01-26T00:49:58+00:00

Return PTR_ERR(led_dat->pwm) instead of 0 if pwm_request failed

Signed-off-by: Axel Lin 
Cc: Richard Purdie 
Cc: Luotao Fu 
Cc: Reviewed-by: Dmitry Torokhov 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

drivers/leds/ledtrig-gpio.c: make output match input, tighten input checking

2011-01-21T01:02:06+00:00

Replicate changes made to drivers/leds/ledtrig-backlight.c.

Cc: Paul Mundt 
Cc: Richard Purdie 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

leds: add output inversion option to backlight trigger

2011-01-13T16:03:06+00:00

Extend the LED backlight tirgger driver with an option that allows for
inverting the trigger output polarity.

With the invertion option provided, I (ab)use the backlight trigger for
driving a LED that indicates LCD display blank condtition on my Amstrad
Delta videophone.  Since the machine has no dedicated power LED, it was
not possible to distinguish if the display was blanked, or the machine was
turned off, without touching it.

The invert sysfs control is patterned after a similiar function of the GPIO
trigger driver.

[akpm@linux-foundation.org: make output match input, tighten input checking]
[akpm@linux-foundation.org: make output match input, tighten input checking]
Signed-off-by: Janusz Krzysztofik 
Cc: Paul Mundt 
Acked-by: Richard Purdie 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

leds-lp5521: modify the way of setting led device name

2011-01-13T16:03:06+00:00

Currently the led device name is fetched from the device_type in
I2C_BOARD_INFO which comes from the platform data.  This name is in turn
used to create an entry in sysfs.

If there exists two or more lp5521 on a particular platform, the
device_type in I2C_BOARD_INFO has to be the same, else lp5521 driver probe
wont be called and if used so, results in run time warning "cannot create
sysfs with same name" and hence a failure.

The name that is used to create sysfs entry is to be passed by the struct
led_platform_data.  Hence adding an element of type const char * and
change in lp5521 driver to use this name in creating the led device if
present else use the name obtained by I2C_BOARD_INFO.

Signed-off-by: Arun Murthy 
Acked-by: Samu Onkalo 
Cc: Ilkka Koskinen 
Cc: Richard Purdie 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

leds: lp5521: fix circular locking

2011-01-13T16:03:06+00:00

Driver contained possibility for circular locking.

One lock is held by sysfs-core and another one by the driver itself.  This
happened when the driver created or removed sysfs entries dynamically.
There is no real need to do those operations.  Now all the sysfs entries
are created at probe and removed at removal.  Engine load sysfs entries
are now visible all the time.  However, access to the entries fails if the
engine is disabled or running.

Signed-off-by: Samu Onkalo 
Cc: Arun Murthy 
Reviewed-by: Ilkka Koskinen 
Cc: Richard Purdie 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

leds: lp5523: fix circular locking

2011-01-13T16:03:05+00:00

Driver contained possibility for circular locking.

One lock is held by sysfs-core and another one by the driver itself.  This
happened when the driver created or removed sysfs entries dynamically.
There is no real need to do those operations.  Now all the sysfs entries
are created at probe and removed at removal.  Engine load and mux
configuration sysfs entries are now visible all the time.  However, access
to the entries fails if the engine is disabled or running.

Signed-off-by: Samu Onkalo 
Cc: Arun Murthy 
Reviewed-by: Ilkka Koskinen 
Cc: Richard Purdie 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds