diff options
| author | Matthew Hagan <mnhagan88@gmail.com> | 2022-02-24 02:50:40 +0300 |
|---|---|---|
| committer | Florian Fainelli <f.fainelli@gmail.com> | 2022-02-25 03:47:25 +0300 |
| commit | 482c85c7fc95c572d368b2214b9e9d2c4a2e5789 (patch) | |
| tree | 655c508d26502b416f4909079b12109378942e22 /arch/arm/boot/dts/bcm958625-meraki-kingpin.dtsi | |
| parent | 66848aff05f669e95795b5f3a163f4762781333e (diff) | |
| download | linux-482c85c7fc95c572d368b2214b9e9d2c4a2e5789.tar.xz | |
ARM: dts: NSP: MX6X: correct LED function types
Currently, the amber LED will remain always on. This is due to a
misinterpretation of the LED sub-node properties, where-by "default-state"
was used to indicate the initial state when powering on the device. When in
use, however, this resulted in the amber LED always being on. Instead change
this to only indicate a fault state.
Assign LED_FUNCTION_POWER to the green PWM LED.
These changes bring the MX64/65 in line with the MR32's devicetree.
Signed-off-by: Matthew Hagan <mnhagan88@gmail.com>
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Diffstat (limited to 'arch/arm/boot/dts/bcm958625-meraki-kingpin.dtsi')
| -rw-r--r-- | arch/arm/boot/dts/bcm958625-meraki-kingpin.dtsi | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/arch/arm/boot/dts/bcm958625-meraki-kingpin.dtsi b/arch/arm/boot/dts/bcm958625-meraki-kingpin.dtsi index 7c487c74fd10..576cfc52567b 100644 --- a/arch/arm/boot/dts/bcm958625-meraki-kingpin.dtsi +++ b/arch/arm/boot/dts/bcm958625-meraki-kingpin.dtsi @@ -106,10 +106,9 @@ led-a { /* amber:power */ - function = LED_FUNCTION_POWER; + function = LED_FUNCTION_FAULT; color = <LED_COLOR_ID_AMBER>; gpios = <&gpioa 0 GPIO_ACTIVE_LOW>; - default-state = "on"; }; led-b { |