tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
fork atom

leds: centralize definition of "default-state" property

Four different drivers define the "default-state" property.
Move this into the common.txt common LEDs properties.

Cc: devicetree@vger.kernel.org
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>

authored by

Linus Walleij and committed by
Jacek Anaszewski 1d1a77dd 7f866986

+13 -16
+7
Documentation/devicetree/bindings/leds/common.txt
··· 19 19 a device, i.e. no other LED class device can be assigned the same 20 20 label. 21 21 22 + - default-state : The initial state of the LED. Valid values are "on", "off", 23 + and "keep". If the LED is already on or off and the default-state property is 24 + set the to same value, then no glitch should be produced where the LED 25 + momentarily turns off (or on). The "keep" setting will keep the LED at 26 + whatever its current state is, without producing a glitch. The default is 27 + off if this property is not present. 28 + 22 29 - linux,default-trigger : This parameter, if present, is a 23 30 string defining the trigger assigned to the LED. Current triggers are: 24 31 "backlight" - LED will act as a back-light, controlled by the framebuffer
+1 -1
Documentation/devicetree/bindings/leds/leds-bcm6328.txt
··· 49 49 - active-low : Boolean, makes LED active low. 50 50 Default : false 51 51 - default-state : see 52 - Documentation/devicetree/bindings/leds/leds-gpio.txt 52 + Documentation/devicetree/bindings/leds/common.txt 53 53 - linux,default-trigger : see 54 54 Documentation/devicetree/bindings/leds/common.txt 55 55
+1 -1
Documentation/devicetree/bindings/leds/leds-bcm6358.txt
··· 28 28 - active-low : Boolean, makes LED active low. 29 29 Default : false 30 30 - default-state : see 31 - Documentation/devicetree/bindings/leds/leds-gpio.txt 31 + Documentation/devicetree/bindings/leds/common.txt 32 32 - linux,default-trigger : see 33 33 Documentation/devicetree/bindings/leds/common.txt 34 34
+2 -7
Documentation/devicetree/bindings/leds/leds-gpio.txt
··· 14 14 see Documentation/devicetree/bindings/leds/common.txt 15 15 - linux,default-trigger : (optional) 16 16 see Documentation/devicetree/bindings/leds/common.txt 17 - - default-state: (optional) The initial state of the LED. Valid 18 - values are "on", "off", and "keep". If the LED is already on or off 19 - and the default-state property is set the to same value, then no 20 - glitch should be produced where the LED momentarily turns off (or 21 - on). The "keep" setting will keep the LED at whatever its current 22 - state is, without producing a glitch. The default is off if this 23 - property is not present. 17 + - default-state: (optional) The initial state of the LED. 18 + see Documentation/devicetree/bindings/leds/common.txt 24 19 - retain-state-suspended: (optional) The suspend state can be retained.Such 25 20 as charge-led gpio. 26 21 - panic-indicator : (optional)
+2 -7
Documentation/devicetree/bindings/leds/register-bit-led.txt
··· 23 23 see Documentation/devicetree/bindings/leds/common.txt 24 24 - linux,default-trigger : (optional) 25 25 see Documentation/devicetree/bindings/leds/common.txt 26 - - default-state: (optional) The initial state of the LED. Valid 27 - values are "on", "off", and "keep". If the LED is already on or off 28 - and the default-state property is set the to same value, then no 29 - glitch should be produced where the LED momentarily turns off (or 30 - on). The "keep" setting will keep the LED at whatever its current 31 - state is, without producing a glitch. The default is off if this 32 - property is not present. 26 + - default-state: (optional) The initial state of the LED 27 + see Documentation/devicetree/bindings/leds/common.txt 33 28 34 29 Example: 35 30