From 6ea5f7d44c8dccdf018af0aa9750903308aa95b7 Mon Sep 17 00:00:00 2001 From: Sungbo Eo Date: Wed, 30 Oct 2019 00:18:35 +0900 Subject: ramips: fix MTK_SOC for RT3662 devices rt3883.mk contains both RT3662 and RT3883 device profiles, but commit 6a104ac77206 set MTK_SOC to rt3883 for all devices. This patch fixes it, and renames dts files accordingly. And SoC compatible strings are also appended in the dts. Fixes: 6a104ac77206 ("ramips/rt288x,rt3883: Name DTS files based on scheme") Signed-off-by: Sungbo Eo --- .../linux/ramips/dts/rt3662_edimax_br-6475nd.dts | 180 +++++++++++++++++++++ 1 file changed, 180 insertions(+) create mode 100644 target/linux/ramips/dts/rt3662_edimax_br-6475nd.dts (limited to 'target/linux/ramips/dts/rt3662_edimax_br-6475nd.dts') diff --git a/target/linux/ramips/dts/rt3662_edimax_br-6475nd.dts b/target/linux/ramips/dts/rt3662_edimax_br-6475nd.dts new file mode 100644 index 0000000000..9e6d98f95a --- /dev/null +++ b/target/linux/ramips/dts/rt3662_edimax_br-6475nd.dts @@ -0,0 +1,180 @@ +/dts-v1/; + +#include "rt3883.dtsi" + +#include +#include + +/ { + compatible = "edimax,br-6475nd", "ralink,rt3662-soc", "ralink,rt3883-soc"; + model = "Edimax BR-6475nD"; + + aliases { + led-boot = &led_power; + led-failsafe = &led_power; + led-running = &led_power; + led-upgrade = &led_power; + }; + + keys { + compatible = "gpio-keys-polled"; + poll-interval = <100>; + + reset { + label = "reset"; + gpios = <&gpio0 7 GPIO_ACTIVE_LOW>; + linux,code = ; + }; + + rfkill { + label = "rfkill"; + gpios = <&gpio0 9 GPIO_ACTIVE_LOW>; + linux,input-type = ; + linux,code = ; + }; + }; + + leds { + compatible = "gpio-leds"; + + led_power: power { + label = "br-6475nd:green:power"; + gpios = <&gpio0 10 GPIO_ACTIVE_LOW>; + }; + + wlan { + label = "br-6475nd:amber:wlan"; + gpios = <&gpio0 11 GPIO_ACTIVE_LOW>; + }; + + wlan_5ghz { + label = "br-6475nd:amber:wlan_5ghz"; + gpios = <&gpio0 14 GPIO_ACTIVE_LOW>; + }; + }; + + nor-flash@1c000000 { + compatible = "cfi-flash"; + reg = <0x1c000000 0x800000>; + bank-width = <2>; + + partitions { + compatible = "fixed-partitions"; + #address-cells = <1>; + #size-cells = <1>; + + partition@0 { + reg = <0x00000000 0x00030000>; + label = "u-boot"; + read-only; + }; + + partition@30000 { + reg = <0x00030000 0x00010000>; + label = "nvram"; + read-only; + }; + + factory: partition@40000 { + reg = <0x00040000 0x00010000>; + label = "factory"; + read-only; + }; + + devdata: partition@50000 { + reg = <0x00050000 0x00020000>; + label = "devdata"; + read-only; + }; + + partition@70000 { + compatible = "edimax,uimage"; + reg = <0x00070000 0x00790000>; + label = "firmware"; + }; + }; + }; + + rtl8367 { + compatible = "realtek,rtl8367"; + gpio-sda = <&gpio0 5 GPIO_ACTIVE_HIGH>; + gpio-sck = <&gpio0 4 GPIO_ACTIVE_HIGH>; + realtek,extif0 = <1 0 1 1 1 1 1 1 2>; + }; + + /* + * Unclear if this is the correct gpio setup; the USB ports are + * unpopulated on a stock BR-6475nD, even though the hardware exists + * and the headers are there. + */ + /* + gpio_export { + compatible = "gpio-export"; + #size-cells = <0>; + + usb { + gpio-export,name="usb"; + gpio-export,output=<0>; + gpios = <&gpio0 19 GPIO_ACTIVE_LOW>; + }; + }; + */ +}; + +&pinctrl { + state_default: pinctrl0 { + gpio { + ralink,group = "spi", "jtag", "uartf"; + ralink,function = "gpio"; + }; + }; +}; + +&timer { + status = "okay"; +}; + +&gpio1 { + status = "okay"; +}; + +&uartlite { + status = "okay"; +}; + +ðernet { + status = "okay"; + mtd-mac-address = <&devdata 0x0d>; + + port@0 { + mediatek,fixed-link = <1000 1 1 1>; + }; +}; + +&wmac { + status = "okay"; + ralink,mtd-eeprom = <&factory 0>; +}; + +&pci { + status = "okay"; +}; + +&pci1 { + status = "okay"; + + wifi@0,0 { + compatible = "pci0,0"; + reg = <0x10000 0 0 0 0>; + ralink,5ghz = <0>; + ralink,mtd-eeprom = <&factory 0x8000>; + }; +}; + +&ehci { + status = "okay"; +}; + +&ohci { + status = "okay"; +}; -- cgit v1.2.3