ramips: use consistent naming scheme for LEDs

The upstream LED naming convention is "device:color:led-name", but it seems that many of supported boards in OpenWrt don't follow this approach.
The following patch fixes this inconsistency in dts{,i} files and updates base-files scripts for ramips target:
 * fixes wrong indentation
 * keeps case statements structure in same convention as in other scripts (no empty line after ";;", no indentation for case...esac body)
 * fixes wrong LED names for some of boards (makes them the same as in dts{,i} files)
 * combines boards with same configuration (ex. set_wifi_led "rt2800pci-phy0::radio" in 01_leds)

Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>

SVN-Revision: 46664

1 files changed, 6 insertions, 6 deletions

diff --git a/target/linux/ramips/dts/3G300M.dts b/target/linux/ramips/dts/3G300M.dts
index 1f9d6f9..997c081 100644
--- a/target/linux/ramips/dts/3G300M.dts
+++ b/target/linux/ramips/dts/3G300M.dts
@@ -57,32 +57,32 @@
 		compatible = "gpio-leds";
 
 		3grouter {
-			label = "tenda:blue:3grouter";
+			label = "3g300m:blue:3grouter";
 			gpios = <&gpio0 11 1>;
 		};
 
 		ap {
-			label = "tenda:blue:ap";
+			label = "3g300m:blue:ap";
 			gpios = <&gpio0 12 1>;
 		};
 
 		wisprouter {
-			label = "tenda:blue:wisprouter";
+			label = "3g300m:blue:wisprouter";
 			gpios = <&gpio0 9 1>;
 		};
 
 		wirelessrouter {
-			label = "tenda:blue:wirelessrouter";
+			label = "3g300m:blue:wirelessrouter";
 			gpios = <&gpio0 13 1>;
 		};
 
 		3g {
-			label = "tenda:blue:3g";
+			label = "3g300m:blue:3g";
 			gpios = <&gpio0 7 1>;
 		};
 
 		wpsreset {
-			label = "tenda:blue:wpsreset";
+			label = "3g300m:blue:wpsreset";
 			gpios = <&gpio0 14 1>;
 		};
 	};