aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* ipq40xx: OpenMesh A42 overhaulChristian Lamparter2018-03-143-88/+81
| | | | | | | | | | | Sort the soc entries in the dts by address and use dtc labels whenever possible. Adjust the DTS files, the OpenMesh A42 is actually an IPQ4018 and not an IPQ4019. Signed-off-by: Sven Eckelmann <sven.eckelmann@openmesh.com> Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: fix apss cpu overclocking spamChristian Lamparter2018-03-142-2/+113
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | There's an interaction issue between the clk changes:" clk: qcom: ipq4019: Add the apss cpu pll divider clock node clk: qcom: ipq4019: remove fixed clocks and add pll clocks " and the cpufreq-dt. cpufreq-dt is now spamming the kernel-log with the following: [ 1099.190658] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for freq 761142857 (-34) This only happens on certain devices like the Compex WPJ428 and AVM FritzBox!4040. However, other devices like the Asus RT-AC58U and Meraki MR33 work just fine. The issue stem from the fact that all higher CPU-Clocks are achieved by switching the clock-parent to the P_DDRPLLAPSS (ddrpllapss). Which is set by Qualcomm's proprietary bootcode as part of the DDR calibration. For example, the FB4040 uses 256 MiB Nanya NT5CC128M16IP clocked at round 533 MHz (ddrpllsdcc = 190285714 Hz). whereas the 128 MiB Nanya NT5CC64M16GP-DI in the ASUS RT-AC58U is clocked at a slightly higher 537 MHz ( ddrpllsdcc = 192000000 Hz). Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx/ipq806x: move qcom-dwc3 usb driver to genericMathias Kresin2018-03-142-66/+0
| | | | | | | If the a kernel package exists within multiple targets an error/warning is shown. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ipq40xx: add targetJohn Crispin2018-03-1451-0/+25706
| | | | | | Signed-off-by: Christian Lamparter <chunkeey@gmail.com> Signed-off-by: Mathias Kresin <dev@kresin.me> Signed-off-by: John Crispin <john@phrozen.org>
* ipq806x: drop ipq40xx supportJohn Crispin2018-03-1448-15076/+3
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* kernel: use V10 of mtd patchset adding support for "compatible" stringRafał Miłecki2018-03-1414-272/+548
| | | | | | | | | | | | | In the commit bde5e7a632ef0 ("kernel: backport mtd implementation for "compatible" in "partitions" subnode") patches that got accepted into l2-mtd.git were backported to the kernels 4.9 and 4.14. Unfortunately there was a regression report, patches were dropped and never reached 4.16. This commit replaces these pseudo-backports with the latest version that includes regression fix and futher changes that were requested. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: mt7620n: add mdio node and disable port4 by defaultMathias Kresin2018-03-131-1/+8
| | | | | | | | | | | | | | | | | Revert the changes I applied to aa5014dd1a58 ("ramips: mt7620n: enable port 4 as EPHY by default"). The driver expects a node mdio-bus to be present, regardless of the actual node status. If the node is missing the driver fails to load with mtk_soc_eth 10100000.ethernet: no mdio-bus child node found Disable port4 by default again. If the port is enabled but not present, a "invalid port id 4" warning is shown during boot. Fixes: FS#1428 Signed-off-by: Mathias Kresin <dev@kresin.me>
* Revert "ramips: gpio: fix compilation if CONFIG_GPIO_SYSFS=n"John Crispin2018-03-131-3/+12
| | | | | | | | This reverts commit cff2dedebc665dc1d3d64d850afd0124c6d35eaa. This patch causes build issues Signed-off-by: John Crispin <john@phrozen.org>
* kernel: b53: drop support for old location of bcm47xx_nvram.hRafał Miłecki2018-03-131-3/+1
| | | | | | | | In kernels 4.0 and older that header file was located in some subdir of arch/mips/include. Target brcm47xx supports kernels 4.4 and 4.9 only so that code isn't needed anymore. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: gpio: fix compilation if CONFIG_GPIO_SYSFS=nAndré Draszik2018-03-131-12/+3
| | | | | | | | | | | | | | | If CONFIG_GPIO_SYSFS=n, compilation fails with drivers/built-in.o: In function `gpio_export_with_name': include/asm-generic/gpio.h:128: undefined reference to `__gpiod_export' This is because the stub in that case has the wrong name, _gpiod_export() - note the missing underscore (_) at the start. Fix the stub, and add the correct prototype for the real implementation. Signed-off-by: André Draszik <git@andred.net>
* swconfig: convert swdevs_lock from spinlock to mutexFelix Fietkau2018-03-121-3/+3
| | | | | | Should fix some sleep-while-atomic issues Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: merge a pending fix for HFSC warnings/slowdowns (fixes FS#1136)Felix Fietkau2018-03-119-9/+267
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: unroll MIPS r4k cache blast functionFelix Fietkau2018-03-103-7/+180
| | | | | | | | | | | Optimize the compiler output for larger cache blast cases that are common for DMA-based networking. On ar71xx, I measured a routing throughput increase of ~8% Signed-off-by: Ben Menchaca <ben.menchaca@qca.qualcomm.com> Signed-off-by: Rosen Penev <rosenp@gmail.com> Signed-off-by: Felix Fietkau <nbd@nbd.name>
* sunxi: Fix B53 swconfig driver for Lamobo R1Hauke Mehrtens2018-03-101-0/+88
| | | | | | | | This reverts the changes needed for the upstream b53 DSA switch driver to use the OpenWrt b43 swconfig switch driver instead. Tested-by: TheWerthFam <thewerthfam@gmail.com> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* sunxi: NanoPi NEO Plus2 backport Gigabit Ethernet DT nodeAntony Antony2018-03-101-3/+21
| | | | | | Kernel 4.16 commit 27d7f9297027 Signed-off-by: Antony Antony <antony@phenome.org>
* mvebu: new subtarget cortex A53Tomasz Maciej Nowak2018-03-1026-6/+1806
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit introduces new subtarget for Marvell EBU Armada Cortex A53 processor based devices. The first device is Globalscale ESPRESSObin. Some hardware specs: SoC: Marvell Armada 3700LP (88F3720) dual core ARM Cortex A53 processor up to 1.2GHz RAM: 512MB, 1GB or 2GB DDR3 Storage: SATA interface µSD card slot with footprint for an optional 4GB EMMC 4MB SPI NOR flash for bootloader Ethernet: Topaz Networking Switch (88E6341) with 3x GbE ports Connectors: USB 3.0 USB 2.0 µUSB port connected to PL2303SA (USB to serial bridge controller) for UART access Expansion: 2x 46-pin GPIO headers for accessories and shields with I2C, GPIOs, PWM, UART, SPI, MMC, etc MiniPCIe slot Misc: Reset button, JTAG interface Currently booting only from µSD card is supported. The boards depending on date of dispatch can come with various U-Boot versions. For the newest version 2017.03-armada-17.10 no manual intervention should be needed to boot OpenWrt image. For the older ones it's necessary to modify default U-Boot environment: 1. Interrupt boot process to run U-Boot command line, 2. Run following commands: (for version 2017.03-armada-17.06 and 2017.03-armada-17.08) setenv bootcmd "load mmc 0:1 0x4d00000 boot.scr; source 0x4d00000" saveenv (for version 2015.01-armada-17.02 and 2015.01-armada-17.04) setenv bootargs "console=ttyMV0,115200 root=/dev/mmcblk0p2 rw rootwait" setenv bootcmd "ext4load mmc 0:1 ${fdt_addr} armada-3720-espressobin.dtb; ext4load mmc 0:1 ${kernel_addr} Image; booti ${kernel_addr} - ${fdt_addr}" saveenv 3. Poweroff, insert SD card with OpenWrt image, boot and enjoy. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: Add subtarget for Cortex A9 buildHauke Mehrtens2018-03-104-158/+181
| | | | | | This is in preparation for adding a subtarget for the Cortex A53 later. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: add support for Turris OmniaRyan Mounce2018-03-106-3/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds support for the Turris Omnia and builds an eMMC sysupgrade image in the same format as the SolidRun ClearFog. An initramfs image in the simple yet Omnia-specific 'medkit' image format is also built in order to ease the initial flashing process. Notable hardware support omissions are support for switching between SFP cage and copper PHY, and RGB LED control. Due to a current limitation of DSA, only 1/2 CPU switch uplinks are used. Specifications: - Marvell Armada 385 1.6GHz dual-core ARMv7 CPU - 1GB DDR3 RAM - 8GB eMMC Flash - 5x Gigabit LAN via Marvell 88E6176 Switch (2x RGMII CPU ports) - 1x switchable RJ45 (88E1514 PHY) / SFP SGMII WAN - 2x USB 3.0 - 12x dimmable RGB LEDs controlled by independent MCU - 3x Mini PCIe slots - Optional Compex WLE200N2 Mini PCIe AR9287 2x2 802.11b/g/n (2.4GHz) - Optional Compex WLE900VX Mini PCIe QCA9880 3x3 802.11ac (2.4 / 5GHz) - Optional Quectel EC20 Mini PCIe LTE modem Flash instructions: If the U-Boot environment has been modified previously (likely manually via serial console), first use serial to reset the default environment. => env default -a => saveenv Method 1 - USB 'medkit' image w/o serial - Copy openwrt-mvebu-turris-omnia-sysupgrade.img.gz and omnia-medkit-openwrt-mvebu-turris-omnia-initramfs.tar.gz to the root of a USB flash drive formatted with FAT32 / ext2/3/4 / btrfs / XFS. Note that the medkit MUST be named omnia-medkit*.tar.gz - Disconnect other USB devices from the Omnia and connect the flash drive to either USB port. - Power on the Omnia and hold down the rear reset button until 4 LEDs are illuminated, then release. - Wait approximately 2 minutes for the Turris Omnia to flash itself with the temporary image, during which LEDs will change multiple times. - Connect a computer to a LAN port of the Turris Omnia with a DHCP client - (if necessary) ssh-keygen -R 192.168.1.1 - ssh root@192.168.1.1 $ mount /dev/sda1 /mnt $ sysupgrade /mnt/openwrt-mvebu-turris-omnia-sysupgrade.img.gz - Wait another minute for the final OpenWrt image to be flashed. The Turris Omnia will reboot itself and you can remove the flash drive. Method 2 - TFTP w/ serial - Extract omnia-medkit-openwrt-mvebu-turris-omnia-initramfs.tar.gz and copy dtb + zImage to your TFTP server (rename if desired) - Connect Turris Omnia WAN port to DHCP-enabled network with TFTP server - Connect serial console and interrupt U-Boot => dhcp => setenv serverip <tftp_server_ip_here> => tftpboot 0x01000000 zImage => tftpboot 0x02000000 dtb => bootz 0x01000000 - 0x02000000 - OpenWrt will now boot from ramdisk - Download openwrt-mvebu-turris-omnia-sysupgrade.img.gz to /tmp/ $ sysupgrade /tmp/openwrt-mvebu-turris-omnia-sysupgrade.img.gz - Wait another minute for the final OpenWrt image to be flashed. The Turris Omnia will reboot itself. Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
* mvebu: generate ramdisk image by defaultRyan Mounce2018-03-091-1/+1
| | | | | | | ramdisk images must be used in the installation process for upcoming Turris Omnia support. Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
* mvebu: disable DSA DT nodes for boards using mvsw61xxRyan Mounce2018-03-092-1/+31
| | | | | | | | As at this commit, DSA is not enabled in the kernel config for mvebu, so these nodes have been ignored. In preparation for the first mvebu board using DSA, disable these nodes for existing boards to avoid issues. Signed-off-by: Ryan Mounce <ryan@mounce.com.au>
* kernel: bump 4.9 to 4.9.86Koen Vandeputte2018-03-095-169/+22
| | | | | | | | | | - Refreshed all patches - Removed 1 patch which got upstreamed Compile tested on: ar71xx (Rocket M5, Mikrotik RB2011) Runtime tested on: ar71xx (Rocket M5, Mikrotik RB2011) Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* kernel: bump to version 4.14.25Kabuli Chana2018-03-0926-249/+78
| | | | | | compile/test target mvebu/rango Signed-off-by: Kabuli Chana <newtownBuild@gmail.com>
* ar71xx: fix double registration of usb host mode devices, add usb client ↵Felix Fietkau2018-03-091-17/+26
| | | | | | | | | | | support for qca955x Only register the chipidea usb device if the strapping option indicates device mode. If not, use the regular ehci platform driver. Add qca955x device mode support, tested on 8devices Rambutan. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* uml: Remove 4.4 patchesFlorian Fainelli2018-03-083-465/+0
| | | | Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* bcm53xx: include patch adding WZR-900DHP LEDs supportRafał Miłecki2018-03-072-0/+190
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* 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>
* ramips: mt7620n: enable port 4 as EPHY by defaultGiuseppe Lippolis2018-03-061-5/+5
| | | | | | | | | | | | According to the datasheet the mt7620n have a fixed switch configuration with 5 ephy (10/100) port. No RGMII configuration is possible. Drop the mdio node as well. Without RGMII, the mdio node doesn't make any sense Signed-off-by: Giuseppe Lippolis <giu.lippolis@gmail.com> [drop mdio node, enable port4 by default] Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: mt7620: power up ephy port 4Pawel Dembicki2018-03-062-0/+2
| | | | | | | | | | | In some boards port 4 of mt7620 switch is powered down in bootloader configuration as lan/wan package leak mitigation. Reset ephy port 4 to default settings to power up the port. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> [clarify issue in commit message] Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: fix mii bus irq assignmentFelix Fietkau2018-03-042-3/+3
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ar71xx: remove pdata->fifo_cfg*Felix Fietkau2018-03-043-56/+3
| | | | | | The values are the same for all chipsets that use it Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: bump 4.4 to 4.4.119Stijn Segers2018-03-0327-145/+126
| | | | | | | | | | | | | | | | | | This bumps the 4.4. kernel in master to 4.4.119. Includes more Meltdown & Spectre mitigation. * Refresh patches. * Refresh x86/config for RETPOLINE. * Deleted 8049-PCI-layerscape-Add-fsl-ls2085a-pcie-compatible-ID.patch (accepted upstream) * Deleted 8050-PCI-layerscape-Fix-MSG-TLP-drop-setting.patch (accepted upstream) * Deleted 650-pppoe_header_pad.patch (does not apply anymore (code was replaced)). Bumps from 4.4.112 to 4.4.115 were handled by Kevin Darbyshire-Bryant. Compile-tested on: ar71xx & oxnas. Signed-off-by: Stijn Segers <foss@volatilesystems.org> Tested-by: Rosen Penev <rosenp@gmail.com>
* kernel: bump 4.9 to 4.9.85Magnus Kroken2018-03-0324-68/+27
| | | | Signed-off-by: Magnus Kroken <mkroken@gmail.com>
* kernel: generic: Add kernel configuration optionsHauke Mehrtens2018-03-021-1/+10
| | | | | | These options are needed for the mvebu arm64 target. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.14 to 4.14.23Stijn Segers2018-03-0217-185/+29
| | | | | | | | | | | | | This patch bumps the 4.14 kernel to .23. - Refreshed patches. - Deleted bcm53xx/patches-4.14/089-PCI-iproc-Fix-NULL-pointer-dereference-for-BCMA.patch. Has been accepted upstream. - Deleted generic/pending-4.14/821-usb-Remove-annoying-warning-about-bogus-URB.patch. The upstream URB code was changed, the patch no longer applies. I discussed this with the patch author and removed it for now, we'll see how it goes. Compile-tested on: ramips/mt7621, x86/64 Run-tested on: ramips/mt7621, x86/64 Signed-off-by: Stijn Segers <foss@volatilesystems.org>
* mvebu: base-files: moving on from net-toolsTomasz Maciej Nowak2018-03-021-4/+4
| | | | | | | Remove dependency on net-tools, replacing calls to ifconfig with iproute equivalent, in functions changing interface MAC addresses. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: rename clearfog sysupgrade script and functionsTomasz Maciej Nowak2018-03-022-5/+5
| | | | | | | | Cosmetic name change of ClearFog sysupgrade script and its functions to more generic sdcard. This way it won't be confusing for other future device additions. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: remove fs declaration in mount commandsTomasz Maciej Nowak2018-03-022-2/+3
| | | | | | | Allows to have other file system for boot partition without breaking sysupgrade. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: unify boot.scr creationTomasz Maciej Nowak2018-03-023-13/+8
| | | | | | | Unify boot.scr generation so Makefile for device image generation won't grow without a reason. Also make boot-scr step optional. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: make sdcard bootloader option configurableTomasz Maciej Nowak2018-03-022-10/+21
| | | | | | | Remove the necessity for boot loader from SD card image creation process and make it configurable. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: fix partition type and signature for sdcardTomasz Maciej Nowak2018-03-022-4/+7
| | | | | | | | | | | Previously the partition signature was assigned from provided type. Now both are corrected wherein signature is always generated from SOURCE_DATE_EPOCH. With that the root file system can be identified by PARTUUID string, without relying on static declaration of device node. This commit also does some cosmetics, removing trailing whitespace and replacing spaces with tab. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: remove redefinition of image name for clearfogTomasz Maciej Nowak2018-03-021-2/+0
| | | | | | | | The IMAGE_NAME redefinition causes overwriting of generated SD card image when multiple root file system types are selected. In result only single SD card image is generated. This commit fixes this behaviour. Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: clearfog: use partition uuid for root= bootargJosua Mayer2018-03-022-12/+14
| | | | | | | | | | | U-Boot already knows where it found the boot.scr, and figuring out the partition UUID becomes trivial at this point. This change allows booting OpenWrt from whatever storage it has been flashed to: SD card, eMMC, USB disk or SATA disk. Signed-off-by: Josua Mayer <josua.mayer97@gmail.com> [replace lede with openwrt, redact commit message] Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
* mvebu: Use kernel 4.14 by defaultHauke Mehrtens2018-03-021-1/+1
| | | | | | I am not aware of any regressions in kernel 4.14 compared to kernel 4.9. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* mvebu: activate more workarounds for ARM erratasHauke Mehrtens2018-03-022-0/+2
| | | | | | | | | The Armada XP uses a Marvell PJ4Bv7 Processor for which already one workaround for an errata is activated. The Armada 285 uses a Cortex A9 r4p1 for which the Linux kernel provides a workaround for ERRATA_764369, activate this. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: generic: Move config option to genericHauke Mehrtens2018-03-023-2/+1
| | | | | | | This is deactivated in all targets using the DSA switch driver with kernel 4.14. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ar71xx: fix build with ag71xx debugfs support enabledFelix Fietkau2018-02-281-6/+4
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ag71xx: Move timestamp struct member outside of struct.Rosen Penev2018-02-282-4/+3
| | | | | | | | | | | | | | | With this change, the timestamp variable is only used in ag71xx_check_dma_stuck. Small tx speedup. Based on a Qualcomm commit. ag->timestamp = jiffies was not replaced with netif_trans_update(dev) because of this quote: It should be noted that after this series several instances of netif_trans_update() are useless (if they occur in .ndo_start_xmit and driver doesn't set LLTX flag -- stack already did an update). From: http://lists.openwall.net/netdev/2016/05/03/87 Signed-off-by: Rosen Penev <rosenp@gmail.com>
* ramips: fix spurious IRQ7 events when using perf on 4.14Felix Fietkau2018-02-271-0/+15
| | | | | | | | | | | | | Upstream handling of MIPS CPU IRQs is rather hackish and the interrupts are being enabled unconditionally in various places because of legacy code. Performance counter events are routed both through the GIC and through legacy CPU IRQ7 events, causing spurious interrupts. Fix this by disabling IRQ7 when trying to access the performance counter IRQ. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* bcm53xx: fix fallback code for picking status LEDRafał Miłecki2018-02-271-1/+1
| | | | | | | | Looking for a wrong LED file name was stopping this code from find any LED. This affects devices with only a red/amber power LED. Fixes: 3aaee1ba023ac ("bcm53xx: failsafe support") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* Revert "ramips: improve NAPI polling to increase GRO batch size" (fixes FS#1333)Felix Fietkau2018-02-271-13/+16
| | | | | | This reverts commit 968b8616127a52fe5baff20a1f29ff49ade26bc2. Signed-off-by: Felix Fietkau <nbd@nbd.name>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-18 17:09:47 +0000