linux-stable.git/drivers/leds/led-class.c, branch linux-3.5.y

leds: fixed a coding style issue.

2012-06-12T02:56:24+00:00

Fixed a coding style issue relating to trailing
white space error found by checkpatch.pl tool in drivers/leds/led-class.c

Signed-off-by: Jeffrin Jose 
Signed-off-by: Bryan Wu

leds: simple_strtoul() cleanup

2012-05-29T23:22:31+00:00

led-class.c and ledtrig-timer.c still use simple_strtoul().  Change them
to use kstrtoul() instead of obsolete simple_strtoul().

Also fix the existing int ret declaration to be ssize_t to match the
return type for _store functions in ledtrig-timer.c.

Signed-off-by: Shuah Khan 
Cc: Joe Perches 
Cc: Richard Purdie 
Cc: Bryan Wu 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

led-class: change back LEDS_CLASS to tristate instead of bool

2012-03-23T23:58:35+00:00

After moving some core functions to led-core.c, led-class.c can be built
as module again.

Signed-off-by: Bryan Wu 
Acked-by: Richard Purdie 
Acked-by: Linus Walleij 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Merge branch 'driver-core-next' into Linux 3.2

2012-01-06T19:42:52+00:00

This resolves the conflict in the arch/arm/mach-s3c64xx/s3c6400.c file,
and it fixes the build error in the arch/x86/kernel/microcode_core.c
file, that the merge did not catch.

The microcode_core.c patch was provided by Stephen Rothwell
 who was invaluable in the merge issues involved
with the large sysdev removal process in the driver-core tree.

Signed-off-by: Greg Kroah-Hartman

driver-core: remove sysdev.h usage.

2011-12-22T00:26:03+00:00

The sysdev.h file should not be needed by any in-kernel code, so remove
the .h file from these random files that seem to still want to include
it.

The sysdev code will be going away soon, so this include needs to be
removed no matter what.

Cc: Jiandong Zheng 
Cc: Scott Branden 
Cc: Russell King 
Cc: Kukjin Kim 
Cc: David Brown 
Cc: Daniel Walker 
Cc: Bryan Huntsman 
Cc: Ben Dooks 
Cc: Wan ZongShun 
Cc: Haavard Skinnemoen 
Cc: Hans-Christian Egtvedt 
Cc: Guan Xuetao 
Cc: "Venkatesh Pallipadi
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: "H. Peter Anvin" 
Cc: Grant Likely 
Cc: Richard Purdie 
Cc: Matthew Garrett 
Signed-off-by: Kay Sievers

Revert "leds: save the delay values after a successful call to blink_set()"

2011-11-16T00:41:50+00:00

Revert commit 6123b0e274503a0d3588e84fbe07c9aa01bfaf5d.

The problem this patch intends to solve has alreadqy been fixed by
commit 7a5caabd090b ("drivers/leds/ledtrig-timer.c: fix broken sysfs
delay handling").

Signed-off-by: Johan Hovold 
Cc: Antonio Ospite 
Cc: Johannes Berg 
Cc: Richard Purdie 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

leds: turn the blink_timer off before starting to blink

2011-11-01T00:30:55+00:00

Depending on the implementation of the hardware blinking function in
blink_set(), the led can support hardware blinking for some values of
delay_on and delay_off and fall-back to software blinking for some other
values.

Turning off the blink_timer unconditionally before starting to blink
make sure that a sequence like:

  OFF
  hardware blinking
  software blinking
  hardware blinking

does not leave the software blinking timer active.

Signed-off-by: Antonio Ospite 
Reviewed-by: Johannes Berg 
Cc: Richard Purdie 
Cc: 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

leds: save the delay values after a successful call to blink_set()

2011-11-01T00:30:55+00:00

When calling the hardware blinking function implemented by blink_set(),
the delay_on and delay_off values are not preserved across calls.

Fix that and make the "timer" trigger work as expected when hardware
blinking is available.

BEFORE the fix:
  $ cd /sys/class/leds/someled
  $ echo timer > trigger
  $ cat delay_on delay_off
  0
  0
  $ echo 100 > delay_on
  $ cat delay_on delay_off
  0
  0
  $ echo 100 > delay_off
  $ cat delay_on delay_off
  0
  0

AFTER the fix:
  $ cd /sys/class/leds/someled
  $ echo timer > trigger
  $ cat delay_on delay_off
  0
  0
  $ echo 100 > delay_on
  $ cat delay_on delay_off
  100
  0
  $ echo 100 > delay_off
  $ cat delay_on delay_off
  100
  100

Signed-off-by: Antonio Ospite 
Reviewed-by: Johannes Berg 
Cc: Richard Purdie 
Cc: 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

leds: support automatic start of blinking with ledtrig-timer

2011-05-25T15:39:49+00:00

By setting initial values blink_delay_on and blink_delay_off in a
led_classdev struct, this change starts the blinking when the led is
initialized.

With this patch, you can initialize blink_delay_on and blink_delay_off in
led_classdev with default_trigger set to "timer", and the led will start
up blinking.  The current ledtrig-timer implementation ignores any initial
blink_delay_on/blink_delay_off settings, and requires setting
blink_delay_on/blink_delay_off (typically from userspace) before the led
blinks.

Signed-off-by: Esben Haabendal 
Cc: Richard Purdie 
Cc: Randy Dunlap 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

led_class: fix typo in blink API

2010-12-23T03:43:34+00:00

When I added led_blink_set I had a typo: the return value of the hw
offload is a regular error code that is zero when succesful, and in that
case software emulation should not be used, rather than the other way
around.

Signed-off-by: Johannes Berg 
Cc: Richard Purdie 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds