aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ath79/dts/ar7161_adtran_bsap1880.dtsi
diff options
context:
space:
mode:
authorAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-09-26 17:31:17 +0200
committerAdrian Schmutzler <freifunk@adrianschmutzler.de>2020-10-02 13:51:39 +0200
commit6f96a4d043a9367c6c0d166299d808df764e88e6 (patch)
tree2e67e0c56508f18a424183f0e0cef1f9fa736269 /target/linux/ath79/dts/ar7161_adtran_bsap1880.dtsi
parent365a639f916b4e9a3771cbaa1271153e111ebde6 (diff)
downloadupstream-6f96a4d043a9367c6c0d166299d808df764e88e6.tar.gz
upstream-6f96a4d043a9367c6c0d166299d808df764e88e6.tar.bz2
upstream-6f96a4d043a9367c6c0d166299d808df764e88e6.zip
ath79: remove model name from LED labels
Currently, we request LED labels in OpenWrt to follow the scheme modelname:color:function However, specifying the modelname at the beginning is actually entirely useless for the devices we support in OpenWrt. On the contrary, having this part actually introduces inconvenience in several aspects: - We need to ensure/check consistency with the DTS compatible - We have various exceptions where not the model name is used, but the vendor name (like tp-link), which is hard to track and justify even for core-developers - Having model-based components will not allow to share identical LED definitions in DTSI files - The inconsistency in what's used for the model part complicates several scripts, e.g. board.d/01_leds or LED migrations from ar71xx where this was even more messy Apart from our needs, upstream has deprecated the label property entirely and introduced new properties to specify color and function properties separately. However, the implementation does not appear to be ready and probably won't become ready and/or match our requirements in the foreseeable future. However, the limitation of generic LEDs to color and function properties follows the same idea pointed out above. Generic LEDs will get names like "green:status" or "red:indicator" then, and if a "devicename" is prepended, it will be the one of an internal device, like "phy1:amber:status". With this patch, we move into the same direction, and just drop the boardname from the LED labels. This allows to consolidate a few definitions in DTSI files (will be much more on ramips), and to drop a few migrations compared to ar71xx that just changed the boardname. But mainly, it will liberate us from a completely useless subject to take care of for device support review and maintenance. To also drop the boardname from existing configurations, a simple migration routine is added unconditionally. Although this seems unfamiliar at first look, a quick check in kernel for the arm/arm64 dts files revealed that while 1033 lines have labels with three parts *:*:*, still 284 actually use a two-part labelling *:*, and thus is also acceptable and not even rare there. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
Diffstat (limited to 'target/linux/ath79/dts/ar7161_adtran_bsap1880.dtsi')
-rw-r--r--target/linux/ath79/dts/ar7161_adtran_bsap1880.dtsi8
1 files changed, 4 insertions, 4 deletions
diff --git a/target/linux/ath79/dts/ar7161_adtran_bsap1880.dtsi b/target/linux/ath79/dts/ar7161_adtran_bsap1880.dtsi
index 17e42d7ba0..344241a322 100644
--- a/target/linux/ath79/dts/ar7161_adtran_bsap1880.dtsi
+++ b/target/linux/ath79/dts/ar7161_adtran_bsap1880.dtsi
@@ -21,24 +21,24 @@
compatible = "gpio-leds";
wlan5g {
- label = "bluesocket:green:wifi5g";
+ label = "green:wifi5g";
gpios = <&gpio 8 GPIO_ACTIVE_LOW>;
linux,default-trigger = "phy1tpt";
};
wlan2g {
- label = "bluesocket:green:wifi2g";
+ label = "green:wifi2g";
gpios = <&gpio 7 GPIO_ACTIVE_LOW>;
linux,default-trigger = "phy0tpt";
};
led_status_green: status_green {
- label = "bluesocket:green:status";
+ label = "green:status";
gpios = <&gpio 5 GPIO_ACTIVE_LOW>;
};
led_status_yellow: status_yellow {
- label = "bluesocket:yellow:status";
+ label = "yellow:status";
gpios = <&gpio 4 GPIO_ACTIVE_LOW>;
};
};