From: Jeff Kletsky <git-commits@allycomm.com>
Date: Sun, 20 Jan 2019 22:48:09 +0000 (-0800)
Subject: ath79: fix GL.iNet AR300M family GPIOs/LEDs
X-Git-Url: http://git.lede-project.org./?a=commitdiff_plain;h=ee3120a9db780480e58199f6811c52896f494b1d;p=openwrt%2Fstaging%2Fblocktrron.git

ath79: fix GL.iNet AR300M family GPIOs/LEDs

Change the "status" LED to proper GPIO 12 and "red" naming.

Remove GPIO 2 from definition as a USB LED.

GPIO 2 is used to control power to the USB socket, not an LED.
As such, PWM on the line or typical LED triggers are inappropriate.

Users who wish to control the USB power for custom applications
can manipulate the GPIO through code, or for example, export it
through /sys/class/gpio/export.

Runtime-tested:  GL.iNet AR300M-Lite

Signed-off-by: Jeff Kletsky <git-commits@allycomm.com>
---

diff --git a/target/linux/ath79/dts/qca9531_glinet_gl-ar300m.dtsi b/target/linux/ath79/dts/qca9531_glinet_gl-ar300m.dtsi
index 2a0c4385cd..fe986bdde0 100644
--- a/target/linux/ath79/dts/qca9531_glinet_gl-ar300m.dtsi
+++ b/target/linux/ath79/dts/qca9531_glinet_gl-ar300m.dtsi
@@ -41,13 +41,6 @@
 	leds {
 		compatible = "gpio-leds";
 
-		usb {
-			label = "gl-ar300m:green:usb";
-			gpios = <&gpio 2 GPIO_ACTIVE_LOW>;
-			trigger-sources = <&hub_port>;
-			linux,default-trigger = "usbport";
-		};
-
 		wlan {
 			label = "gl-ar300m:green:wlan";
 			gpios = <&gpio 14 GPIO_ACTIVE_LOW>;
@@ -60,8 +53,8 @@
 		};
 
 		led_status: status {
-			label = "gl-ar300m:green:status";
-			gpios = <&gpio 3 GPIO_ACTIVE_LOW>;
+			label = "gl-ar300m:red:status";
+			gpios = <&gpio 12 GPIO_ACTIVE_LOW>;
 		};
 	};
 };
@@ -78,11 +71,6 @@
 	#address-cells = <1>;
 	#size-cells = <0>;
 	status = "okay";
-
-	hub_port: port@1 {
-		reg = <1>;
-		#trigger-source-cells = <0>;
-	};
 };
 
 &usb_phy {