aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/lantiq
Commit message (Collapse)AuthorAgeFilesLines
* kernel: bump 4.14 to 4.14.82Koen Vandeputte2018-11-221-1/+1
| | | | | | | | | | | Refreshed all patches. Compile-tested: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested: ar71xx, cns3xxx, imx6, x86_64 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Tested-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Tested-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: bump 4.14 to 4.14.79Koen Vandeputte2018-11-051-1/+1
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx, cns3xxx, imx6, x86_64 Runtime-tested on: ar71xx, cns3xxx, imx6, x86_64 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* treewide: use wpad-basic for not small flash targetsMathias Kresin2018-10-162-35/+35
| | | | | | | | | | | | Add out of the box support for 802.11r and 802.11w to all targets not suffering from small flash. Signed-off-by: Mathias Kresin <dev@kresin.me> Mathias did all the heavy lifting on this, but I'm the one who should get shouted at for committing. Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* kernel: bump 4.14 to 4.14.75Koen Vandeputte2018-10-101-1/+1
| | | | | | | | | Refreshed all patches. Compile-tested on: ar71xx, cns3xxx, imx6 Runtime-tested on: ar71xx, cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* mac80211: make ath10k-ct the default ath10kJohn Crispin2018-09-261-1/+1
| | | | | | | | We select ath10k-ct by default, but it is still possible to build the upstream version. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: John Crispin <john@phrozen.org>
* kernel: bump 4.14 to 4.14.67Koen Vandeputte2018-08-281-1/+1
| | | | | | | | | | | | Refreshed all patches. Removed upstreamed patches: - 037-v4.18-0008-ARM-dts-BCM5301x-Fix-i2c-controller-interrupt-type.patch Compile-tested on: cns3xxx, imx6 Runtime-tested on: cns3xxx, imx6 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* treewide: fix some cosmetic glitches in dts filesPaul Wassi2018-08-276-14/+9
| | | | | | | | | | | - fix single spaces hidden by a tab - replace indentation with spaces by tabs - make empty lines empty - drop trailing whitespace - drop unnecessary blank lines Signed-off-by: Mathias Kresin <dev@kresin.me> Signed-off-by: Paul Wassi <p.wassi@gmx.at>
* lantiq: add support for upgrade ledMathias Kresin2018-08-1636-0/+44
| | | | | | | | | | Indicate a (sys)upgrade via leds as well. It brings the lantiq diag.sh script en par with the other implementations using devicetree aliases to define multiple leds for boot status indication. By default, use the boot finished led to indicate an upgrade for now. Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: convert gpio-export to platform driverRené van Dorst2018-08-041-7/+4
| | | | | | | | | | | | Without this patch you will get an error "gpio-export probe deferral not supported" when you try to export i2c expander gpio pins. gpio-export is probed long before i2c-bus and i2c expander are created and it doesn't retry it so none pins are exported. Signed-off-by: René van Dorst <opensource@vdorst.com> apply the change to all instances of the gpio exports patch Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: add support for FritzBox 7312Johann Neuhauser2018-07-185-1/+197
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The FritzBox 7312 is also known as 1&1 WLAN-MODEM. The device is almost the same as FB7330, but only one ETH-Port and no USB. Hardware SoC: Lantiq Xway ARX188 PSB 50812 EL RAM: 64MB DDR1 (Zentel A4S12D40FTP-G5) Ethernet: Atheros 8030 Wireless: Atheros AR9227 b/g/n 2x2 DSL: Lantiq ADSL2+ DECT: Dialog SC14441 Buttons: WiFi, DECT LEDs: Power/DSL, Fon, DECT, WLAN, Info LEDs Power: GPIO#44 (active low) Internet: GPIO#47 (active low) DECT: GPIO#38 (active low) WLAN: GPIO#37 (active low) Info: GPIO#35 (active low) The Fon LED is labeled as internet in avm gpl sources. Buttons WLAN: GPIO#1 (active low) DECT: GPIO#2 (active low) Phy GPIO#03: 25 MHz GPIO#34: Reset (active low) GPIO#39: Int GPIO#42: MII MDIO GPIO#43: MII MDC PCIe GPIO#21: reset (active low) Installation: To install OpenWrt via Eva bootloader, within the first seconds after power on a ftp connection need to be established to the FRITZ!Box at 192.168.178.1 and the the following ftp commands need to be run: ftp> quote USER adam2 ftp> quote PASS adam2 ftp> binary ftp> debug ftp> passive ftp> quote MEDIA FLSH ftp> put /path/to/openwrt-lantiq-xway-avm_fritz7312-squashfs-sysupgrade.bin mtd1 ftp> quote REBOOT Signed-off-by: Johann Neuhauser <johann@it-neuhauser.de>
* lantiq: etop: pass devicetree node to phy driverJohann Neuhauser2018-07-181-0/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use of_mdiobus_register() to pass the ethernet phy node to the phy drivers. This is needed for the at8030 phy driver which needs to know the GPIO which is connected to the ar8030 reset pin. This driver expects a child in gsw/etop node named "mdio-bus", which has the ethernet phys defined: &gsw { phy-mode = "rmii"; phy-handle = <&phy0>; mtd-mac-address = <&ath9k_cal 0xa91>; mtd-mac-address-increment = <(-2)>; mdio-bus { #address-cells = <1>; #size-cells = <0>; reg = <0>; phy0: ethernet-phy@0 { reg = <0>; reset-gpios = <&gpio 34 GPIO_ACTIVE_LOW>; }; }; }; Fallback to mdiobus_register() if no mdio-bus child node exists. This way we don't need to touch all xway dts files, for which we don't know the actual address on the mdio bus. Signed-off-by: Johann Neuhauser <johann@it-neuhauser.de>
* kernel: only optimized for size if small_flashMathias Kresin2018-07-121-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | Add a new config option to allow to select the default compile optimization level for the kernel. Select the optimization for size by default if the small_flash feature is set. Otherwise "Optimize for performance" is set. Add the small_flash feature flag to all (sub)targets which had the optimization for size in their default kernel config. Remove CC_OPTIMIZE_FOR_* symbols from all kernel configs to apply the new setting. Exceptions to the above are: - lantiq, where the optimization for size is only required for the xway_legacy subtarget but was set for the whole target - mediatek, ramips/mt7620 & ramips/mt76x8 where boards should have plenty of space and an optimization for size doesn't make much sense - rb532, which has 128MByte flash Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: enlarge AVM Fritz!Box 3370 flashMichael Kuron2018-07-042-36/+2
| | | | | | | | | | | | | | | | | | | | | | | | | Increase the available flash memory size in AVM Fritz!Box 3370 by incorporating the unused extra partitions located after the ubi partition. Note that users upgrading from a previous OpenWRT version need to re-install from the boot loader to pick up the new partition layout. Available flash space for rootfs+overlay increases from 48MB to 124MB. Reverting to the OEM firmware is still possible (via the recovery utility provided by AVM) as the OEM firmware appears to reformat the config and nand-filesystem partitions upon first boot if necessary. The reserved-kernel and reserved-filesystem partitions are overwritten by the OEM firmware when installing an update, so their contents do not matter. Boot loader and device-specific information (MAC addresses, calibration data, etc.) are not located in NAND flash and remain unharmed by this changed. Tested with OEM firmware 06.54 on device with HWRevision 5 and Micron flash chip. Signed-off-by: Michael Kuron <m.kuron@gmx.de>
* lantiq: backport stp-xway get callback implementationMathias Kresin2018-07-041-0/+47
| | | | | | | | | | | To keep the status of a LED connected to the stp during boot, the get callback is required. If the callback is missing and the LED default state is set to keep in the devicetree, the gpio led driver errors out during load. Fixes: FS#1620 Signed-off-by: Mathias Kresin <dev@kresin.me>
* treewide: gpio-export: add error handlingMathias Kresin2018-06-281-1/+3
| | | | | | | | Check if the GPIO is valid (or set at all). If no GPIO is set in the devicetree, a gpiolib related kernel warning + stacktrace is shown during boot and gpio-export reports GPIOs as exported albeit none really is. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix arcadyan vg3503j switch port indexingMathias Kresin2018-06-211-1/+1
| | | | | | | Both version of the vg3503j have the LAN1 labelled port connected to switch port 4 and the LAN2 labelled port connected to switch port 2. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: atm: fix ifx_atm driver integrationKevin Darbyshire-Bryant2018-06-181-19/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When upstream kernel introduced commit c55fa3cccbc2c672e7f118be8f7484e53a8e9e77 we incorrectly updated our hack integration patch that updates atm/common.c +++ b/net/atm/common.c @@ -62,10 +62,16 @@ static void vcc_remove_socket(struct soc write_unlock_irq(&vcc_sklist_lock); } +struct sk_buff* (*ifx_atm_alloc_tx)(struct atm_vcc *, unsigned int) = NULL; +EXPORT_SYMBOL(ifx_atm_alloc_tx); + static bool vcc_tx_ready(struct atm_vcc *vcc, unsigned int size) { struct sock *sk = sk_atm(vcc); + if (ifx_atm_alloc_tx != NULL) + return ifx_atm_alloc_tx(vcc, size) The correct solution is to drop our ifx_atm_alloc_tx replacement hack entirely and let the kernel do its thing. In reality neither pppoatm or BR2684 interfaces actually hit this code, so the incorrect integration would only be noticed with direct socket calls which we are unaware of a use-case. This is not the solution to pppoatm vc-mux failing to work which started the whole investigation, but let's fix it up anyway. With sincerest thanks to David Woodhouse <dwmw2@infradead.org> & Mathias Kresin <dev@kresin.me>. Tested-on: lantiq, BT HomeHub 5a Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
* lantiq-vdsl-fw: update to provide recent vectoring firmwareDaniel Golle2018-06-151-1/+1
| | | | | | | | | | | | | | Recent Speedport firmware downloads only work over HTTPS, so the user either needs to provide the already downloaded file or install ustream-ssl-* as well as ca-certificates or ca-bundle. So to get VDSL2 with vectoring on xRX200, simply run vdsl_fw_install.sh on the target and either provide the downloaded file as instructed or make sure the device is connected to the Internet and can download that HTTPS url itself. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* Revert "lantiq: get rid of ltq-vdsl-fw"Daniel Golle2018-06-151-0/+1
| | | | | | This reverts commit 0938233fcdef67d969f9429a10761cc640c6d56d. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* kernel: bump 4.14 to 4.14.48Stijn Tintel2018-06-052-88/+2
| | | | | | | | | | | | | | | | | | Remove upstreamed patches: generic/pending/101-clocksource-mips-gic-timer-fix-clocksource-counter-w.patch generic/pending/103-MIPS-c-r4k-fix-data-corruption-related-to-cache-coherence.patch generic/pending/182-net-qmi_wwan-add-BroadMobi-BM806U-2020-2033.patch lantiq/0025-MIPS-lantiq-gphy-Remove-reboot-remove-reset-asserts.patch Update patches that no longer apply: generic/pending/811-pci_disable_usb_common_quirks.patch ath79/0009-MIPS-ath79-add-lots-of-missing-registers.patch Fixes CVE-2018-6412. Compile-tested: octeon, x86/64. Runtime-tested: octeon, x86/64. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: enable THIN_ARCHIVES by defaultSergey Ryazanov2018-05-221-1/+0
| | | | | | | | THIN_ARCHIVES option is enabled by default in the kernel configuration and no one target config disables it. So enable it by default and remove this symbol from target specific configs to keep them light. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: enable FUTEX_PI by defaultSergey Ryazanov2018-05-221-1/+0
| | | | | | | | | New FUTEX_PI configuration symbol enabled if FUTEX and RT_MUTEX symbols are enabled. Both of these symbols are enabled by default in the generic config, so enable FUTEX_PI by default too to keep platform specific configs minimal. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: enable EXPORTFS by defaultSergey Ryazanov2018-05-221-1/+0
| | | | | | | | OVERLAY_FS config symbol selects EXPORTFS since 4.12 kernel, we have OVERLAY_FS enabled by default, so enable EXPORTFS in the generic config of 4.14 and remove this option from platform specific configs. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: disable DRM_LIB_RANDOM by defaultSergey Ryazanov2018-05-221-1/+0
| | | | | | | DRM_LIB_RANDOM config symbol selected only by DRM_DEBUG_MM_SELFTEST which is disable by default, so disable DRM_LIB_RANDOM by default too. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: disable DMA_{NOOP|VIRT}_OPS by defaultSergey Ryazanov2018-05-221-2/+0
| | | | | | | These options do not used by any supported arch, so disable them by default to make arch configs a bit more clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* kernel: disable ARCH_WANTS_THP_SWAP by defaultSergey Ryazanov2018-05-221-1/+0
| | | | | | | | Only one arch (x86_64) enables this option. So disable ARCH_WANTS_THP_SWAP by default and remove referencies to it from all configs (except x86_64) to make them clean. Signed-off-by: Sergey Ryazanov <ryazanov.s.a@gmail.com>
* lantiq: kernel 4.14: use vbus-supply devicetree propertyMathias Kresin2018-05-1725-32/+32
| | | | | | | | It isn't a phy supply, as the phy is still up if the GPIO is low. It rather is the supply for the vbus. A correct setting/definition will be relevant as soon as USB peripheral mode is supported. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: complete AVM FRITZ!Box 3370 supportMathias Kresin2018-05-178-70/+238
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Rename the image and use a compatible string which indicates that only hardware revision 2 and higher is supported. It allows to use the wireless LED, as HWRev 1 uses GPIO#39 for the wireless LED and starting with HWRev 2 GPIO#35 is used for the wireless LED and GPIO#39 for IFX_GPIO_MODULE_EXTPHY_MDIO. The HWREV can be checked by connecting to the fritzbox right after power on via ftp: ftp> quote GETENV HWSubRevision Within the same HW revision 5 of the Fritz!Box 3370 different NAND flash chips are used. Usually it isn't a big deal but depending on the used NAND flash chip, the ECC calculation is done different (and incompatible of course). Boards with a Micron MT29F1G08ABADA NAND flash chip are using the NAND chip to calculate the ECC (on-die). Boards with a Hynix HY27UF081G2M NAND flash chip are doing the ECC calculation in software. Supporting both with a single DTS isn't possible. It might be possible to add a patch selecting the ECC mode dynamicaly based on the found NAND flash chip. But such a patch has no chance to get accepted upstream and most likely need to be touched with every kernel update. Instead two images are created. One for Micron NAND flash chip and one for Hynix NAND flash chip. So far no pattern is known to identify the used flash chip without opening the box. Add the power off GPIO. At least EVA version 2186 sets/keeps the GPIO as input, which will cause a reboot 30sec after power on. For boards with EVA version 2186 the installation is tricky as it has to be finished within the 30sec time frame. The EVA version can be checked by connecting to the fritzbox right after power on via ftp: ftp> quote GETENV urlader-version The ath9k eeprom/caldata is at a different and offset and stored in reverse order (from the last byte to the beginning) on the flash. Reverse the bits to bring the data into the format expected by the ath9k driver. Since the ath9k eeprom is stored in reverse order on flash, we can not use the mac address from the on flash eeprom. Get the MAC address from the tffs instead. Within the same HW revision 5 of the Fritz!Box 3370 both version of the vr9 SoC are used. During preparation of kernel 4.14 support, all devicetree source files were changed to load the vr9 v1.1 and vr9 v1.2 gphy firmware, which fixed the embedded phys for boards using the version 1.2 of the vr9 SoC. While at it, add a trigger to make use of the LAN LED. Setup the build-in switch and add a hint for LuCI two show the ports in order matching the labels on the case Add support for the second USB port and provide the volatage GPIOs. Use GPIO#21 as PCIe reset pin. The lan led is connected to GPIO#38. Name the rootfs partition ubi and remove the mtd/rootfs related kernel bootargs to use the OpenWrt autoprobing based on the partition name. Enable sysupgrade support to allow an upgrade from a running system. Since sysupgrade wasn't supported till now, drop image build code which was added to allow a sysupgrade from earlier OpenWrt versions. Build images that allow an (initial) installation via EVA bootloader. To install OpenWrt via Eva bootloader, within the first seconds after power on a ftp connection need to be established to the FRITZ!Box at 192.168.178.1 and the the following ftp commands need to be run: ftp> quote USER adam2 ftp> quote PASS adam2 ftp> binary ftp> debug ftp> passive ftp> quote SETENV linux_fs_start 0 ftp> quote MEDIA FLSH ftp> put /path/to/openwrt-lantiq-xrx200-FRITZ3370-eva-kernel.bin mtd1 ftp> put /path/to/openwrt-lantiq-xrx200-FRITZ3370-eva-filesystem.bin mtd0 Signed-off-by: Andrea Merello <andrea.merello@gmail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: switch to kernel 4.14Mathias Kresin2018-05-17117-28894/+1
| | | | | | Use kernel 4.14 by default. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: Remove reboot/remove reset assertsMathias Kresin2018-05-071-0/+86
| | | | | | | | | | | | | | | Backport patch accepted upstream which removes the reset asserts of the xrx200 gphy driver on reboot/remove. While doing a global software reset, these bits are not cleared and let some bootloader fail to initialise the GPHYs. The bootloader don't expect these bits to be set, as they aren't during power on. The asserts were a workaround for a wrong syscon-reboot mask. With a mask set which includes the GPHY resets of the first reset register, the resets of the second reset register arn't required any more. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: bump 4.9 to 4.9.96Kevin Darbyshire-Bryant2018-04-262-4/+4
| | | | | | | | | | | | | | | | | | Refresh patches, following required reworking: ar71xx/patches-4.9/930-chipidea-pullup.patch layerscape/patches-4.9/302-dts-support-layercape.patch sunxi/patches-4.9/0052-stmmac-form-4-12.patch Fixes for CVEs: CVE-2018-1108 CVE-2018-1092 Tested on: ar71xx Archer C7 v2 Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com> Tested-by: Arjen de Korte <build+openwrt@de-korte.org>
* build: consolidate fake uImage header build commandsMathias Kresin2018-04-201-2/+2
| | | | | | | | | | | Merge the two existing functions and use a parameter for the type header field. It updates the syntax of the former mpc85xx fake ramdisk header command to be compatible with mkimage from u-boot 2018.03 and fixes the build error spotted by the build bot. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: fix vr9 reboot maskMathias Kresin2018-04-041-1/+1
| | | | | | | We need to reset the GPHYs on reboot as well. Otherwise the bootloader might have issues to reset/find the GPHYs. Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: update kernel 4.14 to 4.14.32Hauke Mehrtens2018-04-034-88/+2
| | | | | | | | | | | | | The following patches are now included upstream: * 0052-MIPS-lantiq-fix-usb-clocks.patch * 0053-MIPS-lantiq-enable-AHB-Bus-for-USB.patch * 0060-lantiq-ase-enable-MFD-SYSCON.patch Closes: FS#1466 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Tested-by: Stijn Segers <foss@volatilesystems.org> Tested-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* lantiq: intel-xway: add vr9 v1.1 phy supportMathias Kresin2018-03-234-0/+264
| | | | | | | | | | | | During upstreaming the intel phy driver, support for the vr9 v1.1 embedded phys got lost. Backport the upstream send patch adding support for the vr9 v1.1 embbeded phys to the driver. Signed-off-by: Mathias Kresin <dev@kresin.me> cosmetic fixes Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: fix DM200 boot with fake uImage headersThomas Nixon2018-03-181-0/+4
| | | | | | | | | | | | | | The latest bootloader versions load the firmware into memory and call `chk_dniimg` (defined in Netgear GPL release), which expects to find three consecutive block-aligned uImages. Add two fake uImage headers after the kernel to fool this check. This wastes up to 128k of space for alignment. The alternative would be to put the rootfs in a second uImage, but this would limit the firmware size to 0x710000 (the number of bytes loaded and verified by the bootloader) instead of 0x7b0000 (the size of the firmware partition). Signed-off-by: Thomas Nixon <tom@tomn.co.uk>
* lantiq: fix AVM initramfs imageValentin Spreckels2018-03-181-0/+1
| | | | | | Create an initramfs that can be used with the EVA bootloader. Signed-off-by: Valentin Spreckels <Valentin.Spreckels@Informatik.Uni-Oldenburg.DE>
* kernel: make mtd patches apply againHauke Mehrtens2018-03-152-12/+12
| | | | | | | | | This makes some of the mtd patches apply again after some generic patches were changed. These problems where found by build bot. Fixes: ac9bcefa3b044 ("kernel: use V10 of mtd patchset adding support for "compatible" string") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* lantiq/xrx200: add usif support to dts filesMartin Schiller2018-03-062-8/+8
| | | | | | | | The Lantiq XRX200 aka VR9 doesn't have an asc0. Instead, there is an USIF module which can either be an UART or a SPI Controller. Signed-off-by: Martin Schiller <ms@dev.tdt.de>
* kernel: bump 4.9 to 4.9.85Magnus Kroken2018-03-031-1/+1
| | | | Signed-off-by: Magnus Kroken <mkroken@gmail.com>
* kernel: m25p80: allow fallback from spi_flash_read to regular SPI transferFelix Fietkau2018-02-262-4/+4
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: optimize for performance by default starting with 4.14Felix Fietkau2018-02-241-0/+2
| | | | | | Keep size optimizations for smaller targets that already switched Signed-off-by: Felix Fietkau <nbd@nbd.name>
* lantiq: kernel 4.14: update dts filesHauke Mehrtens2018-02-2038-159/+794
| | | | | | | | | | | | | | | | | | | | Updated the devicetree source files to make use of the following upstreamed drivers: - xrx200 ethernet phy - reset controller unit - dwc2 - fpi Use our custom xrx200 ethernet phy compatible to support boards, which have switched the vr9 revision during lifetime, with a single devicetree source file. By switching to the dwc2 driver + usb phy framework, we don't need to used our custom gpio power patch and can use a fixed regulator instead. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: cleanup dts filesMathias Kresin2018-02-2055-4194/+4033
| | | | | | | Move common used parts to dtsi. Add labels to nodes and reference nodes via labels in dts files. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: fix usbMathias Kresin2018-02-202-0/+62
| | | | | | | | | | On danube the USB0 registers are at 1e101000 similar to all other lantiq SoCs. On Danube and AR9 the USB core is connected to the AHB bus, hence we need to enable the AHB Bus as well. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: autoselect matching vr9 rev firmwareMathias Kresin2018-02-201-0/+45
| | | | | | | | | | | | Add a custom xrx200 ethernet phy compatible to load the firmware matching the vr9 revision without specifing an expected revision. We have quite a few boards in the tree were later produced ones are using a more recent vr9. It is impossible to distinguish which revision of the vr9 is used without opening the case and removing a heatsink for some of them. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: don't use CPU interrupt controller IPI IRQ domain supportMathias Kresin2018-02-201-0/+271
| | | | | | | | | | | | | | | | This reverts kernel commit 1eed40043579 ("MIPS: smp-mt: Use CPU interrupt controller IPI IRQ domain support"). With the patch applied, the kernel hangs during boot if SMP is active. The Lantiq IRQ controller gets registered first and it directly handles the MIPS native SW1/2 and HW0 - HW5 IRQs. It looks like this controller already registers IRQ 0 - 7 and the generic driver only gets the following IRQs starting later. The upstream discussion can be found at https://www.linux-mips.org/archives/linux-mips/2017-05/msg00059.html. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: select MFD SYSCON for aseMathias Kresin2018-02-201-0/+24
| | | | | | Enable syscon to use it for the RCU MFD on Amazon SE as well. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: update patches and configHauke Mehrtens2018-02-2035-3208/+333
| | | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: kernel 4.14: copy patches, config and dts filesHauke Mehrtens2018-02-20114-0/+28761
| | | | | | | This just copies the patches, configuration and dts files into the directories hich are used for kernel 4.14. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-02 22:49:16 +0000