summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/bcm958625-meraki-alamo.dtsi
diff options
context:
space:
mode:
authorMatthew Hagan <mnhagan88@gmail.com>2022-02-23 23:50:40 +0000
committerFlorian Fainelli <f.fainelli@gmail.com>2022-02-24 16:47:25 -0800
commit482c85c7fc95c572d368b2214b9e9d2c4a2e5789 (patch)
tree655c508d26502b416f4909079b12109378942e22 /arch/arm/boot/dts/bcm958625-meraki-alamo.dtsi
parent66848aff05f669e95795b5f3a163f4762781333e (diff)
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-alamo.dtsi')
-rw-r--r--arch/arm/boot/dts/bcm958625-meraki-alamo.dtsi3
1 files changed, 1 insertions, 2 deletions
diff --git a/arch/arm/boot/dts/bcm958625-meraki-alamo.dtsi b/arch/arm/boot/dts/bcm958625-meraki-alamo.dtsi
index ba01054a76cf..58b7d9fc7574 100644
--- a/arch/arm/boot/dts/bcm958625-meraki-alamo.dtsi
+++ b/arch/arm/boot/dts/bcm958625-meraki-alamo.dtsi
@@ -57,10 +57,9 @@
led-4 {
/* amber:power */
- function = LED_FUNCTION_POWER;
+ function = LED_FUNCTION_FAULT;
color = <LED_COLOR_ID_AMBER>;
gpios = <&gpioa 3 GPIO_ACTIVE_HIGH>;
- default-state = "on";
};
led-5 {