aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux
Commit message (Collapse)AuthorAgeFilesLines
* ar71xx: fold 641-MIPS-ath79-fix-AR934x-OTP-offsets.patch into the patch that ↵Felix Fietkau2017-04-2615-131/+91
| | | | | | it fixes Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ar71xx: Add OTP support for AR934xChris Blake2017-04-261-0/+66
| | | | | | | | | | The patch 523-MIPS-ath79-OTP-support only supports the OTP offsets for AR933x chips, which has changed on newer platforms such as the AR934x. The follwoing change is to add support for reading the OTP on the AR934x. Tested on an Aerohive AP-121. Signed-off-by: Christian Lamparter <chunkeey@googlemail.com> Signed-off-by: Chris Blake <chrisrblake93@gmail.com>
* kernel: remove out of tree direct-io disable hackFelix Fietkau2017-04-269-251/+0
| | | | | | | Direct-IO support has to be enabled for the release build anyway, so this hack is not worth keeping Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ramips: use the ZBT-WE826 power LED for status indicationMathias Kresin2017-04-252-2/+1
| | | | Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add ZBT-WE826 32MB variantMathias Kresin2017-04-259-19/+57
| | | | | | | | The ZBT-WG826 is available with 16 or 32 MByte of flash. Split the device tree source file, rename the currently supported 16 MByte version and add the 32 MByte variant. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: rename Digineo AC1200 Pro to ZBT-WG3526 32MBMathias Kresin2017-04-258-29/+23
| | | | | | | | The Digineo AC1200 Pro is the 32MB flash variant of the ZBT-WG3526 with unpopulated/exposed sdhci slot. Rename to board to the OEM/ODM name and add the sdhci kernel module to use it for multiple clones. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: prepare ZBT-WG3526 for hardware variantsMathias Kresin2017-04-256-11/+14
| | | | | | | | The ZBT-WG3526 is available with 16 or 32 MByte of flash. Rename the current supported 16MByte version to indicate which flash size variant is supported. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add support for ZBT-WE1326Jiawei Wang2017-04-255-0/+120
| | | | | | | | | | | | | | | | | | | Specification: - SoC: MT7621AT, MT7603EN and MT7612EN - Flash: 16 MiB (W25Q128FVSG) - RAM: 512 MiB (EM6GE16EWXD-12H) - Ethernet: 1 x WAN (10/100/1000Mbps) and 4 x LAN (10/100/1000 Mbps) - Others: USB 2.0, micro SD slot, reset button and 8 x LEDs Issues: - Two LEDs for 2.4 GHz and 5 GHz Wi-Fi do not work, can't find GPIOs. - The pwr LED is not GPIO controllable How to install: - The original firmware is OpenWrt, so both LuCI or sysupgrade can be used. - Do not keep settings, for sysupgrade please use the -n option. Signed-off-by: Jiawei Wang <buaawjw@gmail.com>
* ramips: fix ZyXEL Keenetic Omni/Omni II GPIOsAlexey Belyaev2017-04-252-6/+22
| | | | | | | Each GPIO bank has only 24 gpios. Use and enable the correct banks for GPIOs > 24. Signed-off-by: Alexey Belyaev <spider@spider.vc>
* ramips: fix ZyXEL Keenetic Omni switch configAlexey Belyaev2017-04-252-2/+2
| | | | | | | The wan port is connected to switch port 0. Fix the mediatek,portmap as well as the default switch config. Signed-off-by: Alexey Belyaev <spider@spider.vc>
* lantiq: DGN3500: make switch LEDs blink on activityKevin Darbyshire-Bryant2017-04-251-0/+15
| | | | | | | | | | | | | | | | | Make switch port LEDs blink on activity as they do with stock firmware. The u-boot loader sets suitable values in the LED control register that unfortunately get blown away by the linux switch driver init. Restore that value by using driver 'initvals'. 0x0431 is the led control register, the value 0x0960. Each nybble represents each LED's mode (LED3,2,1,0) in this case OFF, 1000LINK+Activity, 100/10LINK+Activity, OFF. Only LED1&2 are physically present. Enabling the blinkenlights exposed the fact that an RRCP packet was being emitted by the switch on all ports every second. Further initvals copied from stock firmware's u-boot driver disabled this 'feature'. Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
* generic: rtl8366rb: add support for initvals from DTSKevin Darbyshire-Bryant2017-04-251-0/+25
| | | | | | | | | Allow per-device initvals in the DTS file for rlt8366rb switches. Shamelessly copies 30494598f891fc4436a49eca55fc31d03c087841 Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
* omap: rework image generation and profilesAlexander Couzens2017-04-246-44/+104
| | | | | | | | | Migrate to new image generation and introduce sdcard generation (based on sunxi). Profile now generated via image/Makefile instead of profiles/ directory. Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* omap: correct CPU_TYPE: omaps are cortext-a8Alexander Couzens2017-04-241-1/+1
| | | | Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* omap/Kconfig: refresh by oldconfigAlexander Couzens2017-04-241-2/+3
| | | | Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* omap/Kconfig: add usb optionsAlexander Couzens2017-04-241-5/+5
| | | | | | including phy and required dma options Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* omap/Kconfig: enable SMPAlexander Couzens2017-04-241-3/+15
| | | | | | the pandaboard is a multicore omap Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* omap/Kconfig: add omap2plus_cpufreqAlexander Couzens2017-04-241-1/+1
| | | | Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
* mediatek: fix sysupgrade board detectionJohn Crispin2017-04-242-5/+10
| | | | | | | boardnames were changed with the recent target update. the sysupgrade board detection was not updated properly. Signed-off-by: John Crispin <john@phrozen.org>
* mediatek: add support for the NAND-ePHY boardJohn Crispin2017-04-244-2/+538
| | | | | | This is the same as the NAND board but gmac1 is wired to an external phy. Signed-off-by: John Crispin <john@phrozen.org>
* mediatek: add DSA multi cpu port supportJohn Crispin2017-04-242-0/+351
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* mediatek: fix support for gmac1 using external PHYJohn Crispin2017-04-244-2/+115
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* ipq8064: fix dwc3-of-simple module unloading for Netgear R7500Thomas Reifferscheid2017-04-242-14/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Without patch unloading the dwc3-of-simple module went stuck after successfully removing hcd.1 during the hcd.0 removal: root@LEDE:/# rmmod dwc3-of-simple [ 21.391846] xhci-hcd xhci-hcd.1.auto: remove, state 1 [ 21.391931] usb usb4: USB disconnect, device number 1 [ 21.397038] xhci-hcd xhci-hcd.1.auto: USB bus 4 deregistered [ 21.401111] xhci-hcd xhci-hcd.1.auto: remove, state 1 [ 21.406685] usb usb3: USB disconnect, device number 1 [ 21.412848] xhci-hcd xhci-hcd.1.auto: USB bus 3 deregistered [ 21.417248] xhci-hcd xhci-hcd.0.auto: remove, state 1 [ 21.422521] usb usb2: USB disconnect, device number 1 followed by nothing. Sometimes a stall CPU was detected, or a kernel panic, or a reboot occurred after a couple of minutes. At the same time unloading the dwc3 module followed by dwc3-of-simple module was working repeatedly. root@LEDE:/# rmmod dwc3 [ 53.827328] xhci-hcd xhci-hcd.1.auto: remove, state 1 [ 53.827412] usb usb4: USB disconnect, device number 1 [ 53.832630] xhci-hcd xhci-hcd.1.auto: USB bus 4 deregistered [ 53.836452] xhci-hcd xhci-hcd.1.auto: remove, state 1 [ 53.842314] usb usb3: USB disconnect, device number 1 [ 53.848412] xhci-hcd xhci-hcd.1.auto: USB bus 3 deregistered [ 53.852542] xhci-hcd xhci-hcd.0.auto: remove, state 1 [ 53.857882] usb usb2: USB disconnect, device number 1 [ 53.863956] xhci-hcd xhci-hcd.0.auto: USB bus 2 deregistered [ 53.867875] xhci-hcd xhci-hcd.0.auto: remove, state 1 [ 53.873696] usb usb1: USB disconnect, device number 1 [ 53.879742] xhci-hcd xhci-hcd.0.auto: USB bus 1 deregistered root@LEDE:/# rmmod dwc3-of-simple root@LEDE:/# For the non-working case, the code was stuck in a readl() in http://lxr.free-electrons.com/source/drivers/usb/host/xhci.c#L91 because http://lxr.free-electrons.com/source/drivers/usb/dwc3/dwc3-of-simple.c#L126 was disabling the wrong clocks when removing hcd.1 (it was disabling the clock of hcd.0). That's why the readl() went stuck when removing hcd.0 The patch however addresses the clock assignment from the Netgear R7500 dts file and backs off the previous attempt. Now unloading and repeated module loading is working just fine. root@LEDE:/# rmmod dwc3-of-simple [ 24.089679] xhci-hcd xhci-hcd.1.auto: remove, state 1 [ 24.089765] usb usb4: USB disconnect, device number 1 [ 24.094856] xhci-hcd xhci-hcd.1.auto: USB bus 4 deregistered [ 24.098963] xhci-hcd xhci-hcd.1.auto: remove, state 1 [ 24.104522] usb usb3: USB disconnect, device number 1 [ 24.111194] xhci-hcd xhci-hcd.1.auto: USB bus 3 deregistered [ 24.115086] xhci-hcd xhci-hcd.0.auto: remove, state 1 [ 24.120396] usb usb2: USB disconnect, device number 1 [ 24.126503] xhci-hcd xhci-hcd.0.auto: USB bus 2 deregistered [ 24.130347] xhci-hcd xhci-hcd.0.auto: remove, state 1 [ 24.135948] usb usb1: USB disconnect, device number 1 [ 24.142085] xhci-hcd xhci-hcd.0.auto: USB bus 1 deregistered root@LEDE:/# Fixes: dwc3-of-simple module unloading for Netgear R7500 Signed-off-by: Thomas Reifferscheid <thomas@reifferscheid.org>
* ipq8064: Fix dwc3 module unloadingThomas Reifferscheid2017-04-241-3/+11
| | | | | | | | | | The patch follows the qualcomm code comments setting SSUSB_CTRL_TEST_POWERDOWN to 0x1 and is testing and clearing the bit during USB superspeed PHY init. According to Andy Gross it needs to be BIT(26). Signed-off-by: Thomas Reifferscheid <thomas@reifferscheid.org> Acked-by: Andy Gross <andy.gross@linaro.org>
* kernel: use skb_cow_head() to deal with cloned skbsÁlvaro Fernández Rojas2017-04-2314-0/+534
| | | | | | | | | | | We need to ensure there is enough headroom to push extra header, but we also need to check if we are allowed to change headers. skb_cow_head() is the proper helper to deal with this. Fixes Ethernet<->WiFi bridge for Raspberry Pi and probably other devices. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* armvirt: merge arm64 as subtarget 64Yousong Zhou2017-04-2312-345/+165
| | | | | | | | | | | | | | | | | | | | Original armvirt target is now subtarget 32. Other than that the built result should remain the same as before Besides old features already available with arm64, the new armvirt/64 subtarget will also have those features originally enabled for armvirt/32 with commit 44ecfc2 ("armvirt: new target") - pl011, uart - pl031, rtc - pl061, gpio - pci-host-generic - virtio_{mmio,pci,net,blk,scsi,9p,console,balloon} - smp with NR_CPUS=4 - cpu-hotplug - ext4 - DEBUG_BUGVERBOSE for debug purposes Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
* ar71xx: fix minor syntax error in /lib/upgrade/platform.shMatthias Schiffer2017-04-221-1/+1
| | | | | | | Fix a '==' that should be a '=' in a test condition. Busybox fortunately doesn't care. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ramips: update DEVICE_PACKAGES for Ubiquiti EdgeRouter XMatthias Schiffer2017-04-221-1/+1
| | | | | | Fixes removal of unneeded kernel modules with per-device rootfs. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
* ramips: add former board names to PSG1218 variantsDaniel Golle2017-04-211-0/+2
| | | | Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* lantiq: improve DGN3500 LED definitionsKevin Darbyshire-Bryant2017-04-212-9/+65
| | | | | | | | | | | | | | | | Add red:internet led on gpio 30 previously claimed as missing. Wifi led was claimed as blue however there are no blue leds on the board at all. Actually there are two wifi leds, green & amber so add definitions for those. Make the newly discovered green wifi led gpio 14 the default. There is no amber power led on this board. The mention of the amber power led in the manual means power red and power green at the same time. Signed-off-by: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> [removed unnecessary aliases, add migration script] Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: dont replace the board nameMathias Kresin2017-04-215-44/+86
| | | | | | | | | | Use fixed led names and add each board variant instead of manipulating the board name. It makes the ramips board name function less different to the one used in other targets and allows to merge them with a common function. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add former used board names to metadataMathias Kresin2017-04-212-0/+8
| | | | | | | | | We need to keep the former used (unmodified) boardname in the metadata. Otherwise an upgrade from an board using the old boardname will be refused. Fixes: a75ce960ac1b ("ramips: use different board names for variants") Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: rename PSG1218 to match labelDaniel Golle2017-04-218-30/+30
| | | | | | | | Fix previous commit to be less ambigous: PSG1218 rev.A = 5 ports, external PA, heatsinks PSG1218 rev.B = 4 ports, internal PA, no heatsinks Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* ramips: split Phicomm PSG1218 and PSG1218K2CDaniel Golle2017-04-219-84/+145
| | | | | | | | | PSG1218 got only 4 Ethernet ports and WAN on port 3 while PSG1218K2C got 5 Ethernet ports and WAN on port 4 Switch to use kmod-kt76x2 instead of kmod-mt76 for both devices while at it. Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* bcm53xx: enable Northstar thermal driverRafał Miłecki2017-04-202-0/+10
| | | | | | | It allows monitoring CPU temp and will shutdown system on critical value. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: backport DT patches for serial, thermal and MDIORafał Miłecki2017-04-2010-2/+576
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* generic: mtd: backport mx25u25635f stateless 4b supportMathias Kresin2017-04-192-1/+30
| | | | | | | | | Use the stateless 4-byte op codes for this flash chip to fix reboot hangs on SoCs expecting the flash chip in 3-byte mode. Fixes: FS#179 Signed-off-by: Mathias Kresin <dev@kresin.me>
* Revert "mvebu: remove linux 4.4 support"Felix Fietkau2017-04-1779-0/+14294
| | | | | | | | This reverts commit 51397d7d95d9f5e210a5557f65de1fa21e6f5921. There are some unresolved random crashes on WRT1900AC v1 that still need to be sorted out Signed-off-by: Felix Fietkau <nbd@nbd.name>
* kernel: update kernel 4.4 to 4.4.61Jo-Philipp Wich2017-04-154-115/+7
| | | | Signed-off-by: Jo-Philipp Wich <jo@mein.io>
* brcm2708: disable CONFIG_BCM2835_THERMAL by defaultRafał Miłecki2017-04-153-0/+3
| | | | | | | | | | | This fixes: Thermal sensors on bcm2835 SoC (BCM2835_THERMAL) [N/m/y/?] (NEW) aborted! This symbol depends on ARCH_BCM2835 so it should be OK to disable it at brcm2708 target only. Fixes: 7d32caa61fb0 ("brcm2708: backport upstream sdhost controller driver") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: backport Broadcom thermal driversRafał Miłecki2017-04-147-0/+1339
| | | | | | This includes driver for Northstar and for Raspberry Pi. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ramips: really drop the rt-n56u factory imageMathias Kresin2017-04-131-1/+0
| | | | | | Remove the stale reference to the factory image. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: fix ath9k default LED changes falloutMathias Kresin2017-04-134-13/+22
| | | | | | | | | | | | | | | | Since 192f0a3db859 ("ath9k: unset the default LED pin if used by platform leds") the default ath9k wireless LED is not set as soon as any pin of the ath ath9k gpio controller is used. All touched boards have leds defined which are using the gpio pins exposed by the ath9k driver but rely on a default set wireless led trigger. Add the wireless leds were missing and setup the wireless phy trigger in userspace. Signed-off-by: Russell Senior <russell@personaltelco.net> Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix Netgear R6220 package selectionMathias Kresin2017-04-131-1/+1
| | | | | | | | | | | | | The Netgear R6220 requires the kmod-usb3 package and misses kmod-usb-ledtrig-usbport package to setup the configured usb led trigger. Drop the already target selected kmod-mt76. Fixes: FS#686 Fixes: 38bee61dab02 ("ramips: add support for Netgear R6220") Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: add RP-N53 pcie wireless eepromMathias Kresin2017-04-131-0/+9
| | | | | | | | | | Fix the PCIe 5GHz wireless by using the on flash eeprom/caldata. Disable the 2.4GHz band as this band has no antennas attached but is enabled in the eeprom/caldata. Fixes: FS#691 Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: fix WHR-600D eeprom dt propertyMathias Kresin2017-04-131-3/+3
| | | | | | | | | | | Fix the PCIe 5GHz wireless by using the ralink mtd-eeprom property as this board have a RT5592 and uses the rt2x00 driver. The mediathek device tree bindings do not work here. Fixes: FS#691 Fixes: d8dd207ea6f2 ("ramips: use the ralink,mtd-eeprom device tree property") Signed-off-by: Mathias Kresin <dev@kresin.me>
* ramips: drop rt-n56u factory imageMathias Kresin2017-04-131-2/+0
| | | | | | | | | | | | | | | | | | | | | | The factory image has an uImage header covering the entire image and not only the kernel. The original uImage header which covers only the kernel is appended to the end of the image. During LEDE boot the uImage rootfs splitter skips the whole filesystem, can't find a valid filesystem magic and panics. The last known working version was OpenWrt 14.07, which simply kept on searching for an uImage header if the first found didn't resulted into a working rootfs. This behaviour is kind of error prone since it could produce false positives. Since the sysupgrade image works fine in combination with the tftp recovery for doing the initial installation of LEDE, simply drop the factory image. Related: FS#462 Signed-off-by: Mathias Kresin <dev@kresin.me>
* cns3xxx: enable mpcore watchdogKoen Vandeputte2017-04-121-1/+1
| | | | Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* cns3xxx: fix mpcore watchdogKoen Vandeputte2017-04-121-5/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The original implementation loaded the count register with (wrong) semi- random values due to its implemenation nature. If the wrongly calulated value was below the kickrate, the WD was triggered and rebooted the system. Rework this, partly based on upstream patches, to dynamically fetch the current clockrate and calculate the proper offset for the WD countdown register. Before: [ 143.800000] count val: 27219720 [ 148.820000] count val: 50623201 [ 153.830000] count val: 96425250 [ 158.830000] count val: 89735401 [ 163.840000] count val: 4756110 After: [ 0.700000] MPCore WD init. clockrate: 299984500 prescaler: 256 countrate: 1171814 timeout: 60s [ 358.530000] count val: 35154751 [ 363.540000] count val: 35154750 [ 368.540000] count val: 35154751 [ 373.550000] count val: 35154750 Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* cns3xxx: refresh kernel configKoen Vandeputte2017-04-121-1/+0
| | | | Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-11 15:56:46 +0000