aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ath79/dts/qca9563_dlink_dir-842-c.dtsi
Commit message (Collapse)AuthorAgeFilesLines
* ath79: increase spi clock for D-Link DIR-842Sebastian Schaper2020-05-261-1/+2
| | | | | | | | | AHB is 258 MHz for this device (CPU_PLL / 3), but there is no difference between 64 MHz and 50 MHz for spi-max-frequency, thus increase to 50 MHz. Tested on revisions C1 and C3. Signed-off-by: Sebastian Schaper <openwrt@sebastianschaper.net>
* ath79: define switch reset-gpios for D-Link DIR-842Sebastian Schaper2020-05-261-8/+2
| | | | | | | | | | GPIO 11 needs to be pulled high for the external gigabit switch to work, this is currently solved via gpio-hog. Replace with phy0 reset-gpios. Tested on revisions C1 and C3. Reset button is still working for reboot, to enter failsafe, and to enter bootloader http recovery. Signed-off-by: Sebastian Schaper <openwrt@sebastianschaper.net>
* treewide: remove dts-v1 identifier from DTSI filesAdrian Schmutzler2019-12-081-1/+0
| | | | | | | | | | | | | | | | The "/dts-v1/;" identifier is supposed to be put once at the beginning of a device tree file. Thus, it makes no sense to provide it a second time in to-be-included DTSI files. This removes the identifier from all DTSI files in /target/linux. Most of the DTS files in OpenWrt do contain the "/dts-v1/;". It is missing for most of the following targets, though: mvebu, ipq806x, mpc85xx, ipq40xx This does not touch ipq806x for now, as the bump to 4.19 is close. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: add support for D-Link DIR-842 C1Jackson Lim2019-08-051-0/+145
Hardware spec of DIR-842 C1: SoC: QCA9563 DRAM: 128MB DDR2 Flash: 16MB SPI-NOR Switch: QCA8337N WiFi 5.8GHz: QCA9888 WiFi 2.4Ghz: QCA9563 USB: circuit onboard, but components are not soldered Flash instructions: 1. Upgrade the factory.bin through the factory web interface or the u-boot failsafe interface. The firmware will boot up correctly for the first time. Do not power off the device after OpenWrt has booted. Otherwise the u-boot will enter failsafe mode as the checksum of the firmware has been changed. 2. Upgrade the sysupgrade.bin in OpenWrt. After upgrading completes the u-boot won't complain about the firmware checksum and it's OK to use now. 3. If you powered off the device before upgrading the sysupgrade.bin, just upgrade the factory.bin through the u-boot failsafe interface and then goto step 2. Signed-off-by: Jackson Lim <jackcolentern@gmail.com> [fix whitespace issues] Signed-off-by: David Bauer <mail@david-bauer.net>