Ticket #2302 (new defect)

Opened 8 years ago

Last modified 8 years ago

led blinks even when brightness is set to 0

Reported by: lindi Owned by: openmoko-kernel
Priority: normal Milestone:
Component: kernel Version: unspecified
Severity: normal Keywords: led trigger
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:
Reproducible:

Description

Steps to reproduce:
1) echo timer > /sys/class/leds/gta02-aux:red/trigger
2) echo 300 > /sys/class/leds/gta02-aux:red/delay_on
3) echo 700 > /sys/class/leds/gta02-aux:red/delay_off
4) echo 0 > /sys/class/leds/gta02-aux:red/brightness
5) cat /sys/class/leds/gta02-aux:red/trigger

Expected results:
5) LED is OFF and trigger is none since Documentation/leds-class.txt says

"You can change the brightness value of a LED independently of the timer trigger. However, if you set the brightness value to LED_OFF it will also disable the timer trigger."

Actual results:
5) LED keeps blinking and trigger is still timer:

none rfkill0 nand-disk rfkill1 mmc0 adapter-online usb-online ac-online battery-charging-or-full battery-charging battery-full [timer] netdev backlight mmc1

I am using andy-tracking d1c828aa7073b356207b967e394d on gta02V5.

Change History

comment:1 Changed 8 years ago by lars

Don't know why, but for whatever reason this has been explicitly disabled in the openmoko tree.
See: http://git.openmoko.org/?p=kernel.git;a=commitdiff;h=dd6553078a7c14152d7c81e7d3923619720f79a6

comment:2 Changed 8 years ago by lindi

Whatever the explanation is, it is breaking the documented API. Please revert the commit or update the API documentation.

Note: See TracTickets for help on using tickets.