Signed-off-by: John Crispin <john@phrozen.org>
The setting mmc-ddr-1_8v in the platform dts leads to read errors. The device is unusable and system reboots in a loop. Because NBG6817 is the only mmc device, I removed it in base dts. The second change removes settings now present in base dts. The third change references was a wrong conversion of constants in the switch settings. Switch now initializes again. Signed-off-by: André Valentin <avalentin@marcant.net>
At the moment we have 2 seperate device tree sources: 1 for ipq8064 soc located in kernel source and 1 custom in LEDE for ipq8065. ipq8064 and ipq8065 SoCs are completely identical except ipq8065 has higher cpu frequencies and adjusted corresponding power supply. This commit makes ipq8065 DTS to contain only specific for ipq8065 DT entries while pulling all the basic SoC stuff from ipq8064 DTS. It makes easier to manage ipq806x device trees and instead of committing changes into 2 seperate equal DTS we are ending up with only 1. It also enables ipq8065 devices to automatically receive changes made in upstream kernel. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
Enable bam dma support for eMMC and SDCC3 in device tree and update nodes to reflect Qualcomm SDK. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
According to Qualcomm SDK usb3 phy suspend should be disabled for ipq806x. This may solve issue on some ipq806x devices that breaks usb3 storage peripherals during system boot. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
Fixing pvs1 bin voltage as found in GPL tarball and Qualcomm SDK. Also adjusting smb208_s2a/b minimum voltage to reflect lowest value in pvs table. Current ipq8065 devices in LEDE choose (based on eFuse data) pvs bin n4, that has correct values in DT, but in future a new device may choose n1 or n6. Without this change n1 is semi-correct and n6 is not available, because OPP driver disregards bins with voltage values that regulator cannot supply. Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
Allows to check cpu temperature. Huge thanks to @hnyman for valuable assistance! Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
Remove the wifi5g LED from the the d7800, r7500 and r7800. Albeit this GPIO is mentioned in the GPL tarball, it doesn't do anything. The 2.4/5 GHz LEDs are connected to the wifi chips and not be controlled from the the userspace. Use the LEDs names/colours as they are used in the board manuals. Merge redundant LED configurations. Use the phy[0|1]tpt trigger for the wireless LEDs. Remove the workarounds for the not controllable wireless LEDs. Fix spi compatible strings and remove superfluous spi-max-frequency parameters. If there are two power leds, use one for indicating normal operation and one for failsafe/upgrade. Keep the on/off state of the main power led during boot. Use the usb pinmux settings from the nbg6817 gpl sources. Signed-off-by: Mathias Kresin <dev@kresin.me>
Set the pinmux to the values found in the GPL tarballs of the boards. Remove pinmux which are is not used (like nand pinmux for spi flash boards). This allows to use the wan orange led of the C2600 which had a wrong pinmux before. Might fix buttons or leds of other boards as well. Fix the LED color and the ledswitch key code of the C2600. Rename the ledgnr to ledswitch. Add support for indication the boot state using LEDs to the D7800, NBG6817, R7500 and R7500v2. Change GPIO active to readable values in D7800, EA8500, R7500, R7500v2 and R7800. Change gpioexport to gpio pinmux. Add proper "drive strenght" to i2c4_pins and use it for RPM on C2600, D7800, EA8500, R7500, R7500v2. Remove pcie pinmux from D7800. Move pinctrl to correct place in NBG6817 and R7800. Signed-off-by: Henryk Heisig <hyniu@o2.pl>
This router is similar to the C2600. Ethernet on WAN + LAN, switch, sysupgrade, LEDs, buttons and WiFi on 2G + 5G do work. The xDSL modem and the POTS/DECT interface are not supported yet. It is not possible to flash LEDE via the TP-Link webinterface. The image need to be signed. The first 0x200 bytes of the image is the TP-Link header including the signature. The signature is not validated by the bootloader. The LEDE image is zeroed in this area. To install LEDE it is necessary to solder a four pin header to JP2. Connect a serial interface to this header and interrupt the autostart of kernel. Transfer the sysupgrade image via TFTP and write it to the serial flash at 0x320000. Signed-off-by: Sebastian Quilitz <zeraphim@x-pantion.de>