The default trigger for the amber lights on lan1 and lan3 were
mistakenly swapped after the device's migration to DSA. This
caused activity on one port to trigger the amber light on the
other port. Swapping their default trigger in the DTS file
fixes that.
Signed-off-by: Adam Elyas <adamelyas@outlook.com>
[minor commit title adjustment, wrap commit message]
Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
(cherry picked from commit
edaf432bf411767f3e8a9e5effc3a416bcac46c7)
lan3_amber {
label = "amber:lan3";
gpios = <&gpio 13 GPIO_ACTIVE_LOW>;
- linux,default-trigger = "dsa-0.0:01:1Gbps";
+ linux,default-trigger = "dsa-0.0:03:1Gbps";
};
lan2_amber {
lan1_amber {
label = "amber:lan1";
gpios = <&gpio 15 GPIO_ACTIVE_LOW>;
- linux,default-trigger = "dsa-0.0:03:1Gbps";
+ linux,default-trigger = "dsa-0.0:01:1Gbps";
};
};