aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* 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>
* cns3xxx: remove linux 4.4 supportKoen Vandeputte2017-04-1224-1294/+0
| | | | Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* arm64: remove linux 4.4 supportFelix Fietkau2017-04-121-350/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* apm821xx: remove 4.4 kernel supportChristian Lamparter2017-04-1223-7119/+0
| | | | Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
* mvebu: remove linux 4.4 supportFelix Fietkau2017-04-1279-14294/+0
| | | | Signed-off-by: Felix Fietkau <nbd@nbd.name>
* arm64: Switch to 4.9 kernelFlorian Fainelli2017-04-112-1/+308
| | | | Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* kernel: Add various arm64-related symbolsFlorian Fainelli2017-04-111-0/+6
| | | | | | | In preparation for bumping arm64 to 4.9, add a bunch of configuration symbols that are available under arm64. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* arm64: Update READMEFlorian Fainelli2017-04-111-7/+2
| | | | | | | Drop sample command line to use against the ARM Foundation v8 model and replace the path to something that matches LEDE's directory structure. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* arm64: Remove Vexpress Foundation supportFlorian Fainelli2017-04-112-49/+0
| | | | | | | | This required us to both download the Foundation emulator but also build a boot wrapper. QEMU is now fully usable and is a much better replacement. Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* ath9k: drop obsolete patchMathias Kresin2017-04-081-1/+0
| | | | | | | Now that the wireless LEDs are added via platform leds this patch isn't required any longer. Signed-off-by: Mathias Kresin <dev@kresin.me>
* ar71xx: add correct named default wireless led by using platform ledsMathias Kresin2017-04-085-43/+28
| | | | | | | | | | | | | Instead of renaming the default wireless led attached to the wireless chip, add a new led using the platform leds with the phy0tpt trigger set in userspace. When switching ar71xx to device tree, the same can be done by using the build in GPIO controller and without adding new bindings. Drop the now unused platform code. Signed-off-by: Mathias Kresin <dev@kresin.me>
* lantiq: drop tffs patchesMathias Kresin2017-04-084-224/+2
| | | | | | | With the fritz-tools a userspace parser for the Tiny Flash File System is available and makes the tffs2 kernel patches obsolete. Signed-off-by: Mathias Kresin <dev@kresin.me>
* firmware: rework fritz-tools packageMathias Kresin2017-04-081-1/+1
| | | | | | | | | | | | | | | | Split the fritz-tools into subpackages. fritz_tffs_read is usefull for all Fritz boards where fritz-cal_extract is only required for the Fritz 4040 at the moment. Rename the tffs related binary to the more catchy name fritz_tffs and move the whole package to utilities since the package doesn't really provide a firmware file. Make the fritz-tools available for all targets and build them shared. The tffs is used by avm on lantiq and ar71xx as well. Tested-by: Christian Lamparter <chunkeey@googlemail.com> Signed-off-by: Mathias Kresin <dev@kresin.me>
* kernel: update MIPS pci fix to the accepted versionMathias Kresin2017-04-083-34/+33
| | | | | | | Fix the list order instead of adjusting the controller scan order. Revert the former required changes to the lantiq PCIe driver. Signed-off-by: Mathias Kresin <dev@kresin.me>
* mediatek: various fixes for v4.9John Crispin2017-04-0731-2581/+4155
| | | | | | | | | | | | | | | * adds MT7530 DSA support * backport latest ethernet driver * add PMIC leds * add auxadc support * add efuse support * add thermal sensor support * add irq affinity support for ethernet still todo * DSA multi cpu support Signed-off-by: John Crispin <john@phrozen.org>
* kernel: move initramfs's init script out of base-filesRafał Miłecki2017-04-041-0/+0
| | | | | | | | Keeping it in base-files was resulting in adding it to the base-files package. This file is meant to be included manually for initramfs images only. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ar71xx: tp-link.mk: always include device version in image and DEVICE_TITLEPiotr Dymacz2017-04-031-54/+54
| | | | | | | | | | | | | | | | | | | | There are currently several supported TP-Link devices without specified version number in image name and/or DEVICE_TITLE (e.g. WBS210, WBS510, TL-WR810N, TL-WA7510N, TL-WPA8630), but vendor website shows that there are already more than one version of them on the market. For devices like Archer C5, which second version is based on a total different platform, missing version number in DEVICE_TITLE (used in menuconfig) might be misleading for users. To make it less confusing for users and easier to maintain in future, include version number in image name and DEVICE_TITLE for all TP-Link devices, even if there is only one version of device at the moment. Also, keep DEVICE_TITLE in same format for all TP-Link devices. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com> Acked-by: John Crispin <john@phrozen.org>
* ar71xx: add userspace support for Mikrotik RB2011iLRon Angeles2017-04-036-2/+11
| | | | | | | | | Kernel/hardware support for this board has been implemented since Chaos Calmer. This set of patches is to get the board identified in userland. This will allow support for things like sysupgrade, configuring initial LED state, configuring initial switch state, etc. Signed-off-by: Ron Angeles <ronangeles@gmail.com>
* ar71xx: add TP-LINK TL-WR841N/ND v12 imageVittorio Gambaletta2017-04-031-1/+7
| | | | | | | | | | | | | This router has the same hardware as TP-LINK TL-WR841N/ND v11 (same FCC ID, same TFTP image name...). If the stock firmware web interface doesn't accept LEDE factory image, it can be flashed via the U-Boot TFTP recovery mode, by long-pressing the reset button after power on. The TFTP image name is wr841nv11_tp_recovery.bin (yes, v11, not v12). Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net>
* build: allow specifying flow-control to grub on serial consolePhilip Prindeville2017-04-031-2/+2
| | | | | | | On the more sophisticated (i.e. deeper FIFO) serial controllers, flow-control might be needed to avoid dropping output. Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
* kernel: update kernel 4.4 to 4.4.59Hauke Mehrtens2017-04-028-28/+28
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: update kernel 4.9 to 4.9.20Hauke Mehrtens2017-04-0211-211/+36
| | | | Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: fix ubi auto attach loggingJohn Crispin2017-04-021-3/+5
| | | | | | The patch is missing a trailing new line Signed-off-by: John Crispin <john@phrozen.org>
* ar71xx: Compex WPJ563 supportChristian Mehlis2017-03-3012-0/+186
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Specification: - SoC: Qualcomm Atheros QCA9563 (775 MHz, MIPS 74Kc) - RAM: 128 MiB - Storage: 16MB NOR flash - Wireless: Built into QCA9563 (Dragonfly), PHY modes b/g/n, 3x3 MIMO - Ethernet: 2x1G Tested and working: - ethernet / switch / lan / wan - 2.4GHz SoC wifi - PCIe - leds - buzzer Ramload: - tftpboot 0x84000000 lede-ar71xx-generic-wpj563-16M-initramfs-uImage.bin - bootm 0x84000000 Install: - tftpboot 0x80500000 lede-ar71xx-generic-wpj563-16M-squashfs-sysupgrade.bin - erase 0x9f030000 +$filesize - erase 0x9f680000 +1 - cp.b $fileaddr 0x9f030000 $filesize Erasing 0x9f680000 is required because uboot defines "bootcmd=bootm 0x9f680000 || bootm 0x9f030000", so it first tries to boot the higher address. I think the 16 mb flash are intended to be used as 8+8mb for a fallback image. In my hardware only the lower address has a bootable image. But to make sure future hardware will boot lede too, I erase one block, so uboot will skip this address. Signed-off-by: Christian Mehlis <christian@m3hlis.de>
* ar8327: Add workarounds for AR8337 switch.Vittorio Gambaletta2017-03-302-1/+62
| | | | | | | | | | | | | | | | RGMII RX delay setting needs to be always specified for AR8337 to avoid port 5 RX hang on high traffic / flood conditions. Also, the HOL registers that set per-port and per-packet-priority buffer sizes are updated with the reduced values suggested by the QCA switch team. Finally, AR8327 reserved register fixups are disabled for the AR8337. This patch is adapted from the Code Aurora QSDK, but with magic values mapped to proper defines. Signed-off-by: Vittorio Gambaletta <openwrt@vittgam.net>
* ar71xx: drop default CONSOLE valuesJohn Crispin2017-03-291-4/+0
| | | | | | Compex boards dont need to set these as they are default. Signed-off-by: John Crispin <john@phrozen.org>
* ar71xx: move Compex WPJ342 to generic build targetChristian Mehlis2017-03-293-7/+10
| | | | Signed-off-by: Christian Mehlis <christian@m3hlis.de>
* ar71xx: move Compex WPJ344 to generic build targetChristian Mehlis2017-03-293-7/+10
| | | | Signed-off-by: Christian Mehlis <christian@m3hlis.de>
* ar71xx: move Compex WPJ531 to generic build targetChristian Mehlis2017-03-293-7/+10
| | | | Signed-off-by: Christian Mehlis <christian@m3hlis.de>
* ar71xx: move Compex WPJ558 to generic build targetChristian Mehlis2017-03-293-7/+10
| | | | Signed-off-by: Christian Mehlis <christian@m3hlis.de>
* ipq8064: fix dwc3-of-simple module unloadingThomas Reifferscheid2017-03-281-14/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 .dtsi file. Most probably it went into openwrt here: https://dev.openwrt.org/browser/trunk/target/linux/ipq806x/patches-3.18/101-ARM-qcom-add-USB-nodes-to-ipq806x-ap148.patch?rev=45261 copied from Qualcomms attempt here: https://lkml.org/lkml/2015/11/20/116 Now unloading and repeated module loading is working just fine, no matter if you'd remove dwc3-of-simple or dwc3. 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 Signed-off-by: Thomas Reifferscheid <thomas@reifferscheid.org>
* ipq8064: Fix dwc3 module unloadingThomas Reifferscheid2017-03-281-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Allow module unloading by fixing a mistake. qcom_dwc3_phy_write_readback() is expecting (phy, offset, mask, value) while the mistake was calling it with (phy, offset, value, mask) The patch is swapping value and mask. Without the patch unloading the dwc3 module was showing a write to QSCRATCH failed and repeated module loading was failing: root@LEDE:/# rmmod dwc3 [ 19.167998] xhci-hcd xhci-hcd.1.auto: remove, state 1 [ 19.168084] usb usb4: USB disconnect, device number 1 [ 19.173371] xhci-hcd xhci-hcd.1.auto: USB bus 4 deregistered [ 19.177134] xhci-hcd xhci-hcd.1.auto: remove, state 1 [ 19.182960] usb usb3: USB disconnect, device number 1 [ 19.189023] xhci-hcd xhci-hcd.1.auto: USB bus 3 deregistered [ 19.192989] qcom-dwc3-usb-phy 110f8830.phy: write: 8000000 to QSCRATCH: 0 FAILED [ 19.199064] xhci-hcd xhci-hcd.0.auto: remove, state 1 [ 19.205912] usb usb2: USB disconnect, device number 1 [ 19.211611] xhci-hcd xhci-hcd.0.auto: USB bus 2 deregistered [ 19.215905] xhci-hcd xhci-hcd.0.auto: remove, state 1 [ 19.221751] usb usb1: USB disconnect, device number 1 [ 19.227307] xhci-hcd xhci-hcd.0.auto: USB bus 1 deregistered [ 19.231795] qcom-dwc3-usb-phy 100f8830.phy: write: 8000000 to QSCRATCH: 0 FAILED root@LEDE:/# modprobe dwc3 [ 29.583343] phy phy-100f8830.phy.4: phy init failed --> -110 [ 29.583399] dwc3 10000000.dwc3: failed to initialize core [ 29.588169] dwc3: probe of 10000000.dwc3 failed with error -110 [ 29.652943] phy phy-110f8830.phy.2: phy init failed --> -110 [ 29.652988] dwc3 11000000.dwc3: failed to initialize core [ 29.657735] dwc3: probe of 11000000.dwc3 failed with error -110 root@LEDE:/# With patch repeated module unloading and loading is working good: root@LEDE:/# rmmod dwc3 [ 22.622214] xhci-hcd xhci-hcd.1.auto: remove, state 1 [ 22.622298] usb usb4: USB disconnect, device number 1 [ 22.627401] xhci-hcd xhci-hcd.1.auto: USB bus 4 deregistered [ 22.631492] xhci-hcd xhci-hcd.1.auto: remove, state 1 [ 22.637054] usb usb3: USB disconnect, device number 1 [ 22.643721] xhci-hcd xhci-hcd.1.auto: USB bus 3 deregistered [ 22.647421] xhci-hcd xhci-hcd.0.auto: remove, state 1 [ 22.652910] usb usb2: USB disconnect, device number 1 [ 22.659219] xhci-hcd xhci-hcd.0.auto: USB bus 2 deregistered [ 22.662768] xhci-hcd xhci-hcd.0.auto: remove, state 1 [ 22.668604] usb usb1: USB disconnect, device number 1 [ 22.674803] xhci-hcd xhci-hcd.0.auto: USB bus 1 deregistered root@LEDE:/# modprobe dwc3 [ 25.404592] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ 25.404694] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1 [ 25.409444] xhci-hcd xhci-hcd.0.auto: hcc params 0x0228f065 hci version 0x100 quirks 0x00010010 [ 25.416589] xhci-hcd xhci-hcd.0.auto: irq 168, io mem 0x10000000 [ 25.426509] hub 1-0:1.0: USB hub found [ 25.431626] hub 1-0:1.0: 1 port detected [ 25.435472] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ 25.439206] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2 [ 25.444573] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM. [ 25.452926] hub 2-0:1.0: USB hub found [ 25.460420] hub 2-0:1.0: 1 port detected [ 25.525037] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller [ 25.525099] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 3 [ 25.529750] xhci-hcd xhci-hcd.1.auto: hcc params 0x0228f065 hci version 0x100 quirks 0x00010010 [ 25.537002] xhci-hcd xhci-hcd.1.auto: irq 169, io mem 0x11000000 [ 25.546583] hub 3-0:1.0: USB hub found [ 25.551997] hub 3-0:1.0: 1 port detected [ 25.555734] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller [ 25.559621] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 4 [ 25.564942] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM. [ 25.573063] hub 4-0:1.0: USB hub found [ 25.580842] hub 4-0:1.0: 1 port detected root@LEDE:/# Fixes: dwc3 module unloading Signed-off-by: Thomas Reifferscheid <thomas@reifferscheid.org>
* ramips: fix pcie irq mapping for mt7621 on v4.9John Crispin2017-03-281-10/+18
| | | | Signed-off-by: John Crispin <john@phrozen.org>
* bcm53xx: put kernel into TRX when building initramfs imagesRafał Miłecki2017-03-271-0/+25
| | | | | | | | | | | Many (most?) devices can't boot raw kernel using tftp and probably none allows flashing it. It's way more usable to have TRX with kernel containing initrams as such an image can be actually flashed. An exception are Buffalo devices which have recovery mode with support for booting kernels over TFTP. For them keep building default images. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* ar71xx: wpj531: fix GPIOs for LEDLeon M. George2017-03-271-4/+4
| | | | | | /sys/devices/platform/leds-gpio/leds/ was not initialised with working LEDs. Signed-off-by: Leon M. George <leon@georgemail.eu>
* ipq8064: enable 2nd USB port on R7500Thomas Reifferscheid2017-03-272-4/+6
| | | | | | | | | Makes use of the syscon tcsr and enables both USB ports. Cleans up qcom-ipq8064.dtsi from previous attempts. Fixes FS#497 Signed-off-by: Thomas Reifferscheid <thomas@reifferscheid.org>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-11 22:07:19 +0000