brcm63xx: use more systematic names for image and DTS files

This changes brcm63xx target to achieve consistency between image
names, device nodes names, compatible, DTS name and device name
as much as possible. As with other targets, having consistent
names is supposed to make life easier for developers and reduces
the number of "variables" in the system. In particular, applying
the DTS scheme will make it easier to find the correct file and
architecture.

DTS files are named based on the increasingly common
soc-vendor-model scheme, using hyphens for separation as this seems
to be the kernel way. Since the compatible is not used at the
moment, I took the chance to also align them with this patch.

For the SOC, the already existing CFE_CHIP_ID can be exploiting
for all but two devices.

Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>

1 files changed, 118 insertions, 0 deletions

diff --git a/target/linux/brcm63xx/dts/bcm6368-observa-vh4032n.dts b/target/linux/brcm63xx/dts/bcm6368-observa-vh4032n.dts
new file mode 100644
index 0000000000..48f35b16e7
--- /dev/null
+++ b/target/linux/brcm63xx/dts/bcm6368-observa-vh4032n.dts
@@ -0,0 +1,118 @@
+/dts-v1/;
+
+#include "bcm6368.dtsi"
+
+#include <dt-bindings/input/input.h>
+
+/ {
+	model = "Observa VH4032N";
+	compatible = "observa,vh4032n", "brcm,bcm6368";
+
+	chosen {
+		bootargs = "rootfstype=squashfs,jffs2 noinitrd console=ttyS0,115200";
+		stdout-path = "serial0:115200n8";
+	};
+
+	keys {
+		compatible = "gpio-keys-polled";
+		#address-cells = <1>;
+		#size-cells = <0>;
+		poll-interval = <20>;
+
+		reset {
+			label = "reset";
+			gpios = <&pinctrl 34 1>;
+			linux,code = <KEY_RESTART>;
+			debounce-interval = <60>;
+		};
+
+		wlan {
+			label = "wlan";
+			gpios = <&pinctrl 35 1>;
+			linux,code = <KEY_WLAN>;
+			debounce-interval = <60>;
+		};
+	};
+
+	leds {
+		compatible = "gpio-leds";
+
+		dsl_blue {
+			label = "VH4032N:blue:dsl";
+			gpios = <&pinctrl 2 1>;
+		};
+		dsl_red {
+			label = "VH4032N:red:dsl";
+			gpios = <&pinctrl 5 1>;
+		};
+		hspa_blue {
+			label = "VH4032N:blue:hspa";
+			gpios = <&pinctrl 11 1>;
+		};
+		hspa_red {
+			label = "VH4032N:red:hspa";
+			gpios = <&pinctrl 12 1>;
+		};
+		power_blue {
+			label = "VH4032N:blue:power";
+			gpios = <&pinctrl 22 0>;
+			default-state = "on";
+		};
+		power_red {
+			label = "VH4032N:red:power";
+			gpios = <&pinctrl 24 0>;
+		};
+		voice_blue {
+			label = "VH4032N:blue:voice";
+			gpios = <&pinctrl 25 1>;
+		};
+		voice_red {
+			label = "VH4032N:red:voice";
+			gpios = <&pinctrl 26 1>;
+		};
+	};
+};
+
+&pinctrl {
+       pinctrl-names = "default";
+       pinctrl-0 = <&pinctrl_pci &pinctrl_ephy0_led &pinctrl_ephy1_led
+		    &pinctrl_ephy2_led &pinctrl_ephy3_led>;
+
+	usb_hub_reset {
+		gpio-hog;
+		gpios = <27 0>;
+		output-high;
+		line-name = "usb-hub-reset-gpio";
+	};
+};
+
+&pflash {
+	status = "ok";
+
+	partitions {
+		compatible = "fixed-partitions";
+		#address-cells = <1>;
+		#size-cells = <1>;
+
+		cfe@0 {
+			label = "CFE";
+			reg = <0x0000000 0x0020000>;
+			read-only;
+		};
+
+		linux@20000 {
+			label = "linux";
+			reg = <0x0020000 0x1fc0000>;
+			compatible = "brcm,bcm963xx-imagetag";
+		};
+
+		nvram@1fe0000 {
+			label = "nvram";
+			reg = <0x1fe0000 0x020000>;
+		};
+	};
+};
+
+&uart0 {
+	status = "ok";
+};