openwrt/target/linux/ath79/dts/qca9533_comfast_cf-e110n-v2.dts

154 lines
2.6 KiB
Plaintext
Raw Normal View History

ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
#include "qca953x.dtsi"
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/input/input.h>
/ {
compatible = "comfast,cf-e110n-v2", "qca,qca9533";
model = "COMFAST CF-E110N v2";
aliases {
serial0 = &uart;
led-boot = &led_rssihigh;
led-failsafe = &led_rssihigh;
led-upgrade = &led_rssihigh;
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
};
leds {
compatible = "gpio-leds";
pinctrl-names = "default";
pinctrl-0 = <&jtag_disable_pins &led_rssilow_pin &led_rssimediumhigh_pin &led_rssihigh_pin>;
wan {
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>
2020-09-26 15:31:17 +00:00
label = "green:wan";
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
gpios = <&gpio 3 GPIO_ACTIVE_LOW>;
};
lan {
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>
2020-09-26 15:31:17 +00:00
label = "green:lan";
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
gpios = <&gpio 2 GPIO_ACTIVE_LOW>;
};
rssilow {
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>
2020-09-26 15:31:17 +00:00
label = "red:rssilow";
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
gpios = <&gpio 11 GPIO_ACTIVE_LOW>;
};
rssimediumlow {
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>
2020-09-26 15:31:17 +00:00
label = "red:rssimediumlow";
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
gpios = <&gpio 12 GPIO_ACTIVE_LOW>;
};
rssimediumhigh {
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>
2020-09-26 15:31:17 +00:00
label = "green:rssimediumhigh";
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
gpios = <&gpio 14 GPIO_ACTIVE_LOW>;
};
led_rssihigh: rssihigh {
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>
2020-09-26 15:31:17 +00:00
label = "green:rssihigh";
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
gpios = <&gpio 16 GPIO_ACTIVE_LOW>;
};
};
ath9k-leds {
compatible = "gpio-leds";
wlan {
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>
2020-09-26 15:31:17 +00:00
label = "green:wlan";
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
gpios = <&gpio 0 GPIO_ACTIVE_LOW>;
linux,default-trigger = "phy0tpt";
};
};
keys {
compatible = "gpio-keys";
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
reset {
label = "reset";
linux,code = <KEY_RESTART>;
gpios = <&gpio 17 GPIO_ACTIVE_LOW>;
debounce-interval = <60>;
};
};
};
&pinmux {
led_rssilow_pin: pinmux_rssilow_pin {
pinctrl-single,bits = <0x8 0x0 0xff000000>;
};
led_rssimediumhigh_pin: pinmux_rssimediumhigh_pin {
pinctrl-single,bits = <0xc 0x0 0x00ff0000>;
};
led_rssihigh_pin: pinmux_rssihigh_pin {
pinctrl-single,bits = <0x10 0x0 0x000000ff>;
};
};
&spi {
status = "okay";
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
flash@0 {
compatible = "winbond,w25q128", "jedec,spi-nor";
reg = <0>;
spi-max-frequency = <25000000>;
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
partition@0 {
label = "u-boot";
reg = <0x000000 0x010000>;
read-only;
};
art: partition@10000 {
label = "art";
reg = <0x010000 0x010000>;
read-only;
};
partition@20000 {
compatible = "denx,uimage";
label = "firmware";
reg = <0x020000 0xfd0000>;
};
partition@ff0000 {
label = "nvram";
reg = <0xff0000 0x010000>;
read-only;
};
};
};
};
&eth0 {
status = "okay";
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
phy-handle = <&swphy4>;
mtd-mac-address = <&art 0x0>;
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
};
&eth1 {
mtd-mac-address = <&art 0x1002>;
gmac-config {
device = <&gmac>;
};
};
&wmac {
status = "okay";
ath79: add support for COMFAST CF-E110N This patch adds support for the COMFAST CF-E110N, an outdoor wireless CPE with two Ethernet ports and a 802.11bgn radio. Specifications: - 650/400/216 MHz (CPU/DDR/AHB) - 2x 10/100 Mbps Ethernet, both with PoE-in support - 64 MB of RAM (DDR2) - 16 MB of FLASH - 2T2R 2.4 GHz, up to 26 dBm - 11 dBi built-in antenna - POWER/LAN/WAN/WLAN green LEDs - 4x RSSI LEDs (2x red, 2x green) - UART (115200 8N1) and GPIO (J9) headers on PCB Flashing instructions: The original firmware is based on OpenWrt so a sysupgrade image can be installed via the stock web GUI. Settings from the original firmware will be saved and restored on the new want, so a factory reset will be needed: once the new firmware is flashed, perform the factory reset by pushing the reset button several times during the boot process, while the WAN LED flashes, until it starts flashing quicker. The U-boot bootloader contains a recovery HTTP server to upload the firmware. Push the reset button while powering the device on and keep it pressed for >10 seconds. The recovery page will be at http://192.168.1.1 Notes: The device is advertised, sold and labeled as "CF-E110N", but the bootloader and the stock firmware identify it as "v2". Acknowledgments: Petr Štetiar <ynezz@true.cz> Sebastian Kemper <sebastian_ml@gmx.net> Chuanhong Guo <gch981213@gmail.com> Signed-off-by: Roger Pueyo Centelles <roger.pueyo@guifi.net> [drop unused labels from devicetree source file] Signed-off-by: Mathias Kresin <dev@kresin.me>
2018-12-10 14:44:56 +00:00
mtd-cal-data = <&art 0x1000>;
mtd-mac-address = <&art 0x6>;
};