aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* kernel: backport GCC 10 usbip build fix for 5.4Rui Salvaterra2021-03-051-0/+33
| | | | | | | | | | | | | | From the original commit message: "With GCC 10, building usbip triggers error for multiple definition of 'udev_context', in: - libsrc/vhci_driver.c:18 and - libsrc/usbip_host_common.c:27. Declare as extern the definition in libsrc/usbip_host_common.c." Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com> (cherry picked from commit 0eef8402ee2ad014121932c860174e6d95440e17)
* kernel: b53: update the BCM5365 UIDDaniel González Cabanelas2021-03-052-4/+4
| | | | | | | | | | | | | | | | | BCM63XX internal PHYs and BCM5365 SoC internal switch are both using the same phy_driver->phy_id, causing conflicts and unnecessary probes. E.g the BCM63XX phy internal IRQ is lost on the first probe. The full BCM5365 UID is 0x00406370. Use an additional byte to mask the BCM5365 UID to avoid duplicate driver phy_id's. This will fix the IRQ issue in internal BCM63XX PHYs and avoid more conflicts in the future. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com> (merge both cherry-picked commits) Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry-picked from commits cbcac4fde8 and cfa43f8119)
* bcm27xx: bcm2711: disable HW_RANDOM_BCM2835Álvaro Fernández Rojas2021-03-051-1/+0
| | | | | | | This driver is only present on BCM2708, BCM2709 and BCM2710. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry-picked from commit bac74aff5e)
* mpc85xx: p2020: fix cfi-nor detectionPawel Dembicki2021-03-011-0/+1
| | | | | | | | | | | | | | | | At this moment p2020rdb has broken images, because NOR memory connected to eLBC bus isn't detected. In 642b1e8dbed7 linux tree commit, config dependencies of MTD_PHYSMAP_OF was changed and now MTD_PHYSMAP is required. This patch adds MTD_PHYSMAP option to kernel config in p2020 subtarget and fix booting of p2020rdb. Fixes: 13b1db795f05 ("mpc85xx: add support for kernel 5.4") Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> (cherry picked from commit 76649fd06d454f1b93f2ee74951ef91225155a8c)
* mvebu/omnia: fix the device treeRui Salvaterra2021-03-013-0/+165
| | | | | | | | | | | | Backport [1] and fix [2] hardware buffer management. Also fix the IRQ storm caused by a misconfiguration of the PCA9538 interrupt pin [3]. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/arm/boot/dts/armada-385-turris-omnia.dts?id=018b88eee1a2efda26ed2f09aab33ccdc40ef18f [2] https://lore.kernel.org/linux-arm-kernel/20210217153038.1068170-1-rsalvaterra@gmail.com/ [3] https://lore.kernel.org/linux-arm-kernel/20210220231144.32325-1-kabel@kernel.org/ Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com> (cherry picked from commit 6fe6b631ef91a8a44d7324329ad6aaec6f08ada6)
* lantiq: set maximum kernel sizeMathias Kresin2021-03-012-0/+4
| | | | | | | | | | | | These boards have a fixed size kernel partition but do not limit the kernel size during image building. Disable image building for both boards as well, since the kernel of the last release as well as master are to big to fit into the 2 MByte kernel partition. Signed-off-by: Mathias Kresin <dev@kresin.me> (cherry picked from commit 23dd7867347ab4fd88592d0bfec1ce5a959c09f3)
* octeon: re-enable CONFIG_CAVIUM_CN63XXP1 and EdgeRouter imageAdrian Schmutzler2021-02-282-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The symbol CONFIG_CAVIUM_CN63XXP1 was disabled during the bump to 4.19 (see Fixes:) with the following reason: No supported hardware uses CN63XXP1 and it causes "slight decrease in performance" However, it later turned out that the edgerouter image needed it, which led to having the device disabled in [1]. Still, dropping support of a device seems a harsh action for just removing a "slight" decrease in performance from the other devices. Thus, this enables CONFIG_CAVIUM_CN63XXP1 again, and essentially restores the situation present until (including) kernel 4.14 on this target. For OpenWrt as a platform, it seems more desirable to support all devices (and have them tested regularly via the snapshots) in this case. Users interested in maximum performance might still just remove the symbol again in their local build. [1] 3824fa26d256 ("octeon: disable edgerouter image") Fixes: 6c22545225cd ("target/octeon: Add Linux 4.19 support") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit cfd1a40583d66d5f6a30dec5bee0f7ebd4d252ef)
* ath79: enable UART node for GL-USB150Adrian Schmutzler2021-02-251-4/+0
| | | | | | | | | | | This was overlooked when adding support for this device. (It has recently been discovered that this was the only device in ath79 having &uart disabled.) Fixes: acc62630132c ("ath79: add support for GL.iNet GL-USB150") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 722f1bd5490abafc5d77420905179aa03c508a1f)
* ath79: enable UART in SoC DTSI filesAdrian Schmutzler2021-02-25208-847/+16
| | | | | | | | | | | | | | | | | | | The uart node is enabled on all devices except one (GL-USB150 *). Thus, let's not have a few hundred nodes to enable it, but do not disable it in the first place. Where the majority of devices is using it, also move the serial0 alias to the DTSI. *) Since GL-USB150 even defines serial0 alias, the missing uart is probably just a mistake. Anyway, disable it for now so this patch stays cosmetic. Apply this to 21.02 as well to remove an unnecessary backporting pitfall. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 3a4b751110b32380cf827f14a203190cfbc2e40f)
* ramips: mt7621: enable SX150x driverSander Vanheule2021-02-241-0/+1
| | | | | | | | | | | | | | | | | The Netgear R6800 and R6700v2 devices have a Semtech SX1503 GPIO expander controlling the device LEDs. This expander was initially supported on 4.14, but support was lost in the transition to 5.4. Since this driver cannot be built as a kernel module, enable it in the kernel config for all mt7621 devices. Run-tested on a Netgear R6800. Cc: Stijn Segers <foss@volatilesystems.org> Cc: Hauke Mehrtens <hauke@hauke-m.de> Signed-off-by: Sander Vanheule <sander@svanheule.net> Tested-by: Stijn Segers <foss@volatilesystems.org> (cherry picked from commit 773949c152f7378a303919e790210113012fea04)
* ramips: overwrite reset gpio properties in DIR-860L DTSStijn Segers2021-02-241-0/+3
| | | | | | | | | | | | | | | As suggested by Sergio, this adds GPIOs 19 and 8 explicitly into the DIR-860L DTS, so the PCI-E ports get reset and the N radio (radio1) on PCI-E port 1 comes up reliably. Fixes the following error that popped up in dmesg: [ 1.638942] mt7621-pci 1e140000.pcie: pcie1 no card, disable it (RST & CLK) Suggested-by: Sergio Paracuellos <sergio.paracuellos@gmail.com> Signed-off-by: Stijn Segers <foss@volatilesystems.org> Reviewed-by: Sergio Paracuellos <sergio.paracuellos@gmail.com> (cherry picked from commit 06356f00200639c48d95330e633965957b0347ab)
* bcm63xx: pinctrl: fix BCM6348 groupsDaniel González Cabanelas2021-02-233-30/+14
| | | | | | | | | | | | | | | | | | | | | The current driver has some troubles: - Some groupings are wrong. - The pinctrl group0 owns pins never used (at least in Openwrt) for any pinmux. The driver hijacks all the pins on the group avoiding any other use, spite they're free. I.e. for buttons, causing this kernel error: [ 4.735928] gpio-keys-polled keys: unable to claim gpio 479, err=-22 [ 4.742642] gpio-keys-polled: probe of keys failed with error -22 - Minor errors about groupings on the documentation - Missing "diag" grouping in dtsi - Wrong groupings in dtsi Fix it by setting the correct groups. And relax the pin capturing, letting the gpios belonging to any group to be used for other purposes like buttons. This was the behavior with stock firmwares and old OpenWrt versions which never caused any trouble. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com> (Cherry-picked from commit 50cb3a750f)
* bcm63xx: limit name metadata to model nameÁlvaro Fernández Rojas2021-02-231-5/+1
| | | | | | | | Since there are only 16 characters available, on most cases the vendor name will fit in the metadata, but the model name won't fit. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry-picked from commit c27532742d)
* ramips: fix Phicomm PSG1218A switch port labelsShiji Yang2021-02-221-1/+1
| | | | | | | | | The lan port sequence was reversed compared to the labels. Signed-off-by: Shiji Yang <yangshiji66@qq.com> [improve commit title/message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 567a88e4b99f9e1b647588de0319357e688ce016)
* ramips: correct/add Phicomm K2x WAN/label MAC addressShiji Yang2021-02-221-4/+4
| | | | | | | | | | | | | | | Phicomm K2G: add missing label_mac Phicomm PSG1218A & PSG1218B: The previous wan mac was set as factory@0x28 +1 (originally based on the default case for the ramips target), but the correct wan mac is factory@0x28 -1, being equal to factory@0x2e. Signed-off-by: Shiji Yang <yangshiji66@qq.com> [minor commit title/message adjustments] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 55263ffedbe1d20f005febbc973a7353240d1741)
* bcm63xx: bcm63268: fix GPIO interruptsÁlvaro Fernández Rojas2021-02-221-1/+1
| | | | | | | pinctrl should rely on external interrupt controller for GPIO interrupts. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry-picked from commit 36e35b8d81)
* bcm27xx: remove urngd packageÁlvaro Fernández Rojas2021-02-201-0/+2
| | | | | | | Now that khwrngd is working on all subtargets we can remove urgnd. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry-picked from commit 9dc84018ee)
* bcm27xx: enable bcm2711 HW RNGÁlvaro Fernández Rojas2021-02-203-0/+27
| | | | | | | Also add a patch setting its quality, which should make it usable by khwrngd. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry-picked from commit 670526efa3)
* generic: add bcm2835-rng quality patchÁlvaro Fernández Rojas2021-02-201-0/+26
| | | | | | | | This patch allows devices without a high resolution timer to boot up faster. It should speed up boots for bcm2708 and bcm63xx. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry-picked from commit 7747b3fa36)
* ramips: overwrite reset gpio properties in EX6150 DTSStijn Segers2021-02-201-0/+3
| | | | | | | | | | | | | | | | The Netgear EX6150 can, just like the D-Link DIR-860L rev B1, fail to initialise both radios in some cases. Add the reset GPIOs explicitly so the PCI-E devices get re-initialised properly. See also FS #3632. Error shows up in dmesg as follows: [ 1.560764] mt7621-pci 1e140000.pcie: pcie1 no card, disable it (RST & CLK) Tested-by: Kurt Roeckx <kurt@roeckx.be> Signed-off-by: Stijn Segers <foss@volatilesystems.org> [removed period from commit title] Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit af1b6799c6ec9af7a30d63a5ddfed20f443b991c)
* layerscape: add new devices in README and clean upYangbo Lu2021-02-191-33/+70
| | | | | | | | | | Support new devices LS1046AFRWY and LX2160ARDB in README. Clean up README, and add missing LS1021ATWR deploy guide. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com> [adjust set of devices added, update commit message/title] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit a31842e7fd15c14796a9f764defda395b3c854df)
* layerscape: add LX2160ARDB (Rev2.0 silicon) board supportYangbo Lu2021-02-192-4/+61
| | | | | | | | | | | | | | | | | | | | | | | The QorIQ LX2160A reference design board provides a comprehensive platform that enables design and evaluation of the LX2160A processor. - Enables network intelligence with the next generation Datapath (DPPA2) which provides differentiated offload and a rich set of IO, including 10GE, 25GE, 40GE, and PCIe Gen4 - Delivers unprecedented efficiency and new virtualized networks - Supports designs in 5G packet processing, network function virtualization, storage controller, white box switching, network interface cards, and mobile edge computing - Supports all three LX2 family members (16-core LX2160A; 12-core LX2120A; and 8-core LX2080A) Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com> [use AUTORELEASE, add dtb to firmware part] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 80dcd14abeed8cd808b92bb307964dbaeb252144)
* layerscape: add FRWY-LS1046A board supportYangbo Lu2021-02-192-0/+46
| | | | | | | | | | | | | | | | | | | | The LS1046A Freeway board (FRWY) is a high-performance computing, evaluation, and development platform that supports the QorIQ LS1046A architecture processor capable of support more than 32,000 CoreMark performance. The FRWY-LS1046A board supports the QorIQ LS1046A processor, onboard DDR4 memory, multiple Gigabit Ethernet, USB3.0 and M2_Type_E interfaces for Wi-Fi. The FRWY-LS1046A-TP includes the Coral Tensor Flow Processing Unit that offloads AI/ML inferencing from the CPU to provide significant boost for AI/ML applications. The FRWY-LS1046A-TP includes one M.2 TPU module and more modules can easily be added including USB versions of the module to scale the AI/ML performance. Signed-off-by: Yangbo Lu <yangbo.lu@nxp.com> [rebase, use AUTORELEASE, fix sorting, add dtb to firmware part] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 2c2d77bd3bd4691c5f8f1760b9ef16f96f345255)
* layerscape: move rework-sdcard-images out of fsl-sdbootAdrian Schmutzler2021-02-192-2/+6
| | | | | | | | Upcoming devices will not need the migration setup, so let's move it out of the common definition. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit a9075d42d7990af230a08bdbb03c14ae2bf27318)
* ramips: use lzma-loader for Wevo devicesSeo Suchan2021-02-191-0/+2
| | | | | | | | | | | As kernel size increased it start to fail to load squishfs image, using lzma-loader fixed it. wevo_11acnas is almost same device as w2914ns-v2 except ram size, so I expect same thing would've happen in that device too. Signed-off-by: Seo Suchan <abnoeh@mail.com> Reviewed-by: Sungbo Eo <mans0n@gorani.run> (cherry picked from commit ca6954e2dc3faa32eec54b93bda996c874409675)
* ramips: mt7621: add TP-Link EAP235-Wall supportSander Vanheule2021-02-193-0/+196
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The TP-Link EAP235-Wall is a wall-mounted, PoE-powered AC1200 access point with four gigabit ethernet ports. When connecting to the device's serial port, it is strongly advised to use an isolated UART adapter. This prevents linking different power domains created by the PoE power supply, which may damage your devices. The device's U-Boot supports saving modified environments with `saveenv`. However, there is no u-boot-env partition, and saving modifications will cause the partition table to be overwritten. This is not an issue for running OpenWrt, but will prevent the vendor FW from functioning properly. Device specifications: * SoC: MT7621DAT * RAM: 128MiB * Flash: 16MiB SPI-NOR * Wireless 2.4GHz (MT7603EN): b/g/n, 2x2 * Wireless 5GHz (MT7613BEN): a/n/ac, 2x2 * Ethernet: 4× GbE * Back side: ETH0, PoE PD port * Bottom side: ETH1, ETH2, ETH3 * Single white device LED * LED button, reset button (available for failsafe) * PoE pass-through on port ETH3 (enabled with GPIO) Datasheet of the flash chip specifies a maximum frequency of 33MHz, but that didn't work. 20MHz gives no errors with reading (flash dump) or writing (sysupgrade). Device mac addresses: Stock firmware uses the same MAC address for ethernet (on device label) and 2.4GHz wireless. The 5GHz wireless address is incremented by one. This address is stored in the 'info' ('default-mac') partition at an offset of 8 bytes. From OEM ifconfig: eth a4:2b:b0:...:88 ra0 a4:2b:b0:...:88 rai0 a4:2b:b0:...:89 Flashing instructions: * Enable SSH in the web interface, and SSH into the target device * run `cliclientd stopcs`, this should return "success" * upload the factory image via the web interface Debricking: U-boot can be interrupted during boot, serial console is 57600 baud, 8n1 This allows installing a sysupgrade image, or fixing the device in another way. * Access serial header from the side of the board, close to ETH3, pin-out is (1:TX, 2:RX, 3:GND, 4:3.3V), with pin 1 closest to ETH3. * Interrupt bootloader by holding '4' during boot, which drops the bootloader into its shell * Change default 'serverip' and 'ipaddr' variables (optional) * Download initramfs with `tftpboot`, and boot image with `bootm` # tftpboot 84000000 openwrt-initramfs.bin # bootm Revert to stock: Using the tplink-safeloader utility from the firmware-utils package, TP-Link's firmware image can be converted to an OpenWrt-compatible sysupgrade image: $ ./staging_dir/host/bin/tplink-safeloader -B EAP235-WALL-V1 \ -z EAP235-WALLv1_XXX_up_signed.bin -o eap235-sysupgrade.bin This can then be flashed using the OpenWrt sysupgrade interface. The image will appear to be incompatible and must be force flashed, without keeping the current configuration. Known issues: - DFS support is incomplete (known issue with MT7613) - MT7613 radio may stop responding when idling, reboot required. This was an issue with the ddc75ff704 version of mt76, but appears to have improved/disappeared with bc3963764d. Error notice example: [ 7099.554067] mt7615e 0000:02:00.0: Message 73 (seq 1) timeout Hardware was kindly provided for porting by Stijn Segers. Tested-by: Stijn Segers <foss@volatilesystems.org> Signed-off-by: Sander Vanheule <sander@svanheule.net> (cherry picked from commit 1e75909a35a2b361cdfdfcf18a26ad61271b174e)
* ramips: remove factory image for TP-Link Archer C20 v1Stijn Segers2021-02-191-0/+1
| | | | | | | | | | | | | Similarly to the Archer C2 v1, the Archer C20 v1 will brick when one tries to flash an OpenWrt factory image through the TP-Link web UI. The wiki page contains an explicit warning about this [1]. Disable the factory image altogether since it serves no purpose. [1] https://openwrt.org/toh/tp-link/tp-link_archer_c20_v1#installation Signed-off-by: Stijn Segers <foss@volatilesystems.org> (cherry picked from commit 0265cba40ad4f2b8ff4473ada123c35b53ffd97a)
* bcm63xx: update ethernet kernel panics fixÁlvaro Fernández Rojas2021-02-197-34/+54
| | | | | | | | Use new patch from Sieng Piaw Liew. Signed-off-by: Sieng Piaw Liew <liew.s.piaw@gmail.com> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry-picked from commit 31a06f8fcc)
* bcm27xx: add diag LEDsÁlvaro Fernández Rojas2021-02-191-0/+7
| | | | | | | | We can now use the power LED for diag in more devices thanks to the latest patches from the RPi foundation. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry-picked from commit 5bab472a11)
* bcm27xx: bcm2708: add missing RPi B DTS fileÁlvaro Fernández Rojas2021-02-191-1/+1
| | | | | | | | | RPI 1B DTS has been splitted into 2 files: - bcm2708-rpi-b.dts: Newest (rev2) RPI 1B - bcm2708-rpi-b-rev1.dts: Old (rev1) RPI 1B Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry-picked from commit 0aaa2cce1c)
* bcm27xx: add support for RPI CM4 and RPI 400Álvaro Fernández Rojas2021-02-192-6/+13
| | | | | | | Support added to bcm2709 (32 bits) and bcm2711 (64 bits). Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry-picked from commit 8ad61118fd)
* bcm27xx: import latest patches from the RPi foundationÁlvaro Fernández Rojas2021-02-19927-703/+41630
| | | | | | | | | | bcm2708: boot tested on RPi B+ v1.2 bcm2709: boot tested on RPi 3B v1.2 and RPi 4B v1.1 4G bcm2710: boot tested on RPi 3B v1.2 bcm2711: boot tested on RPi 4B v1.1 4G Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry-picked from commit f07e572f64)
* kernel: bump 5.4 to 5.4.99John Audia2021-02-1931-89/+87
| | | | | | | | | | | Ran update_kernel.sh in a fresh clone without any existing toolchains. No manual changes needed. Build system: x86_64 Build-tested: bcm27xx/bcm2711 Signed-off-by: John Audia <graysky@archlinux.us> (cherry-picked from commit 5d3a6fd970)
* mediatek: add support for Ubiquiti UniFi 6 LRDavid Bauer2021-02-186-2/+378
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Hardware -------- MediaTek MT7622 512MB DDR3 RAM 64M SPI-NOR Flash (Winbond W25Q512JV) MediaTek MT7622 802.11bgn 4T4R WMAC MediaTek MT7915 802.11ax 4T4R Marvell AQR1112 100/1000/2500 NBase-T PHY Holtek HT32F52241 LED controller Reset Switch UART ---- CPU UART0 at the pinout next to the Holtek MCU. Pinout (first pin next to SoC / MCU) 0 3V3 1 RX 2 TX 3 GND Settings are 115200 8N1. Opening the case ---------------- Opening the case is not a nice task, as itis glued together. Insert a flat knife between the front and back casing below the ethernet port. Open up a gap this way and insert a flat scredriver, remove the knife. Work your way around the casing by applying force to seperate the front and back casing. This losens the glue and opens the plastic clips. Be gentle, as these clips are very cheap and break quickly. Installation ------------ 1. Connect to the booted device at 192.168.1.20 using username/password "ubnt". 2. Transfer the OpenWrt sysupgrade image to the device using SCP. 3. Check the mtd partition number for bs / kernel0 / kernel1 $ cat /proc/mtd 4. Set the bootselect flag to boot from kernel0 $ dd if=/dev/zero bs=1 count=1 of=/dev/mtdblock6 5. Write the OpenWrt sysupgrade image to both kernel0 as well as kernel1 $ dd if=openwrt.bin of=/dev/mtdblock8 $ dd if=openwrt.bin of=/dev/mtdblock9 6. Reboot the device. It should boot into OpenWrt. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit 634c13c186646aff2badb51a43b248825d0fe5a0)
* mediatek: add Ubiquiti LED driverDavid Bauer2021-02-185-0/+242
| | | | | | | | | | | | Add a driver for controlling the RGB LED via Ubiquitis own "LEDBAR" LED controller based on the Holtek HT32F52241 MCU. This driver is initially used by the Ubiquiti UniFi 6 LR, however judging from FCC pictures the MCU is also found on the U6-Mesh as well as the U6-Extender. Signed-off-by: David Bauer <mail@david-bauer.net> (cherry picked from commit c9137e2ddf97ede1db399dc38acff26feb48ba7e)
* lantiq: fritz7320: enable USB power supplyMathias Kresin2021-02-181-0/+46
| | | | | | | | | | | | | The USB ports if a FRIZZ!Box 7320 do not supply power to connected devices. Add the GPIOs enabling USB power as regulator, to enable USB power supply as soon as the USB driver is loaded. Fixes FS#3624 Signed-off-by: Mathias Kresin <dev@kresin.me> (cherry picked from commit 6e4e97b2256327bb380ee2a83da9a1ddf657e395)
* kernel: 5.4: fix .patch file extensionAdrian Schmutzler2021-02-171-0/+0
| | | | | | | | File extension was truncated for pending-5.4/770-11-net-ethernet-mtk_eth_soc-avoid-rearming-interrupt-if.pa Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 487b7ae5ebbbc76e0b2952658432d28eee07f7a2)
* ipq807x: drop targetAdrian Schmutzler2021-02-164-714/+0
| | | | | | This target is not ready for stable release yet. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm4908: fix GPIOs support by limiting them to 64Rafał Miłecki2021-02-151-0/+23
| | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm4908: use DTS patches sent upstreamRafał Miłecki2021-02-155-33/+145
| | | | | | | | There are 2 new patches: 1. Netgear R8000P switch ports 2. Netgear R8000P LEDs Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm4908: add USB packages to the DEFAULT_PACKAGESRafał Miłecki2021-02-151-0/+2
| | | | | | | All known 41 BCM4908 devices have USB ports so it makes sense to include those packages by default. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm4908: fix backport of PMB driverRafał Miłecki2021-02-151-0/+8
| | | | | | | Missing Makefile change was preventing kernel from actually compiling the driver. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: drop ofpart patch dropped from upstream mtd treeRafał Miłecki2021-02-156-236/+653
| | | | | | It stopped ofpart_parser_init() from being called Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: backport "ofpart" mtd parser upstream quirks supportRafał Miłecki2021-02-156-29/+77
| | | | | | | | | | This adds quirks support to the "ofpart" parser. It's required to support fixed partitions that require some extra logic. Right now only BCM4908 binding is supported (BCM4908 requires detecting currently used "firmware" partition). Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: fix busy wait loop in mediatek PPE codeIlya Lipnitskiy2021-02-151-1/+1
| | | | | | | | | | | The intention is for the loop to timeout if the body does not succeed. The current logic calls time_is_before_jiffies(timeout) which is false until after the timeout, so the loop body never executes. time_is_after_jiffies(timeout) will return true until timeout is less than jiffies, which is the intended behavior here. Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com>
* ramips: mark toggle input on EX6150 as a switchKurt Roeckx2021-02-151-0/+1
| | | | | | | | | The Netgear EX6150 has an Access Point/Extender switch. Set it as an EV_SW. Otherwise when it's set to Access Point, it will trigger failsafe mode during boot. Fixes: FS#3590 Signed-off-by: Kurt Roeckx <kurt@roeckx.be>
* Revert "imx6: bootscript-apalis: make it working on v2021.01 release"Petr Štetiar2021-02-141-4/+2
| | | | | | | | This reverts commit 4968fc8fb110612018af3ba2836be1b4744346e2 as the bump to v2021.01 needs swig on the host for pylibfdt which is needed by dtoc tool to generate .h/.c files from DTBs in SPL for mx6cuboxi_config. Signed-off-by: Petr Štetiar <ynezz@true.cz>
* target: fix copying of licenses for SDK/toolchainAdrian Schmutzler2021-02-142-2/+6
| | | | | | | | | | | | | | | The SDK and target/toolchain copy the license file into their directories. During the rename/move from LICENSE to a LICENSES folder, this has not been updated. Update it now, and include the new COPYING file. While at it, improve formatting/indent. Fixes: 882e3014610b ("LICENSES: include all used licenses in LICENSES directory") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ath79: fix factory image generation for Netgear and Zyxel boardsPaul Fertser2021-02-143-4/+2
| | | | | | | | | | | | | The factory images need to embed specific IDs to pass verification with the OEM firmware (including TFTP recovery), so they need to be per-device variables. Fixes: ab1584a797ad ("ath79: netgear: trim down uImage customisations") Fixes: 459c8c9ef816 ("ath79: add support for ZyXEL NBG6616") Reported-by: Marcin Juszkiewicz <marcin-openwrt@juszkiewicz.com.pl> Signed-off-by: Paul Fertser <fercerpav@gmail.com> [minor commit message adjustments, sort DEVICE_VARS] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* mvebu: espressobin: drop COMPHY removement patchTomasz Maciej Nowak2021-02-142-53/+0
| | | | | | | | | | There are proper workarounds merged to 5.4 stable tree for ESPRESSObin boards with older bootloader: 4e1a23779bde ("ata: ahci: mvebu: Make SATA PHY optional for Armada 3720") 40af962eb1d4 ("usb: host: xhci: mvebu: make USB 3.0 PHY optional for Armada 3720") Signed-off-by: Tomasz Maciej Nowak <tmn505@gmail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-10 23:36:59 +0000