aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* ath79: Add support for Buffalo WZR-HP-G300NHMauri Sandberg2021-03-276-5/+335
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This device is a wireless router working on 2.4GHz band based on Qualcom/Atheros AR9132 rev 2 SoC and is accompanied by Atheros AR9103 wireless chip and Realtek RTL8366RB/S switches. Due to two different switches being used also two different devices are provided. Specification: - 400 MHz CPU - 64 MB of RAM - 32 MB of FLASH (NOR) - 3x3:2 2.4 GHz 802.11bgn - 5x 10/100/1000 Mbps Ethernet - 4x LED, 3x button, On/Off slider, Auto/On/Off slider - 1x USB 2.0 - bare UART header place on PCB Flash instruction: - NOTE: Pay attention to the switch variant and choose the image to flash accordingly. (dmesg / kernel logs can tell it) - Methods for flashing - Apply factory image in OEM firmware web-gui. - Sysupgrade on top of existing OpenWRT image - U-Boot TFPT recovery for both stock or OpenWRT images: The device U-boot contains a TFTP server that by default has an address 192.168.11.1 (MAC 02:AA:BB:CC:DD:1A). During the boot there is a time window, during which the device allows an image to be uploaded from a client with address 192.168.11.2. The image will be written on flash automatically. 1) Have a computer with static IP address 192.168.11.2 and the router device switched off. 2) Connect the LAN port next to the WAN port in the device and the computer using a network switch. 3) Assign IP 192.168.11.1 the MAC address 02:AA:BB:CC:DD:1A arp -s 192.168.11.1 02:AA:BB:CC:DD:1A 4) Initiate an upload using TFTP image variant curl -T <imagename> tftp://192.168.11.1 5) Switch on the device. The image will be uploaded subsequently. You can keep an eye on the diag light on the device, it should keep on blinking for a while indicating the writing of the image. General notes: - In the stock firmware the MAC address is the same among all interfaces so it is left here that way too. Recovery: - TFTP method - U-boot serial console Differences to ar71xx platform - This device is split in two different targets now due to hardware being a bit different under the hood. Dynamic solution within the same image is left for later time. - GPIOs for a sliding On/Off switch, marked 'Movie engine' on the device cover, were the wrong way around and were renamed qos_on -> movie_off, qos_off -> movie_on. Associated key codes remained the same they were. The device tree source code is mostly based on musashino's work Signed-off-by: Mauri Sandberg <sandberg@mailfence.com> (cherry picked from commit bc356de2850f14629cb1301be719772fa1212e72)
* ath79: cfi: cmdset_0002: amd chip 0x2201 - write wordsMauri Sandberg2021-03-271-0/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | Generally, in upstream CFI flash memory driver uses buffers for write operations. That does not work with AMD chip with id 0x2201 and we must resort to writing word sized chunks only. That is, to not apply general buffer write functionality for this given chip. Without the patch kernel logs will be flooded with entries like below: MTD do_erase_oneblock(): ERASE 0x01fa0000 MTD do_write_buffer(): WRITE 0x01fa0000(0x00001985) MTD do_erase_oneblock(): ERASE 0x01f80000 MTD do_write_buffer(): WRITE 0x01f80000(0x00001985) MTD do_write_buffer_wait(): software timeout, address:0x01f8000a. jffs2: Write clean marker to block at 0x01a60000 failed: -5 MTD do_erase_oneblock(): ERASE 0x01f60000 MTD do_write_buffer(): WRITE 0x01f60000(0x00001985) MTD do_write_buffer_wait(): software timeout, address:0x01f6000a. jffs2: Write clean marker to block at 0x01a40000 failed: -5 References: http://patchwork.ozlabs.org/project/linux-mtd/patch/20210309174859.362060-1-sandberg@mailfence.com/ Signed-off-by: Mauri Sandberg <sandberg@mailfence.com> [added link to usptream fix submission] Signed-off-by: Petr Štetiar <ynezz@true.cz> (cherry picked from commit 8cc0fa8faceadac85353bb1a96e074518ef124e2)
* ramips: add support for ELECOM WRC-1750GST2INAGAKI Hiroshi2021-03-222-0/+48
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ELECOM WRC-1750GST2 is a 2.4/5 GHz band 11ac (Wi-Fi 5) router, based on MT7621A. Specification: - SoC : MediaTek MT7621A - RAM : DDR3 256 MiB (NT5CC128M16JR-EK) - Flash : SPI-NOR 32 MiB (MX25L25645GMI-08G) - WLAN : 2.4/5 GHz 3T3R (2x MediaTek MT7615) - Ethernet : 10/100/1000 Mbps x5 - Switch : MediaTek MT7530 (SoC) - LEDs/Keys : 4x/6x (2x buttons, 1x slide-switch) - UART : through-hole on PCB - J4: 3.3V, GND, TX, RX, from ethernet port side - 57600n8 - Power : 12 VDC, 1.5 A Flash instruction using factory image: 1. Boot WRC-1750GST2 normally with "Router" mode 2. Access to "http://192.168.2.1/" and open firmware update page ("ファームウェア更新") 3. Select the OpenWrt factory image and click apply ("適用") button 4. Wait ~120 seconds to complete flashing MAC addresses: LAN : 04:AB:18:xx:xx:23 (Factory, 0xE000 (hex)) WAN : 04:AB:18:xx:xx:24 (Factory, 0xE006 (hex)) 2.4GHz : 04:AB:18:xx:xx:25 (Factory, 0x4 (hex)) 5GHz : 04:AB:18:xx:xx:26 (Factory, 0x8004 (hex)) Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com> (cherry picked from commit b3ca1f30efd7bb96a22f72b766d302e552265276)
* ath79: fix lan port display order for sitecom wlr-7100Walter Sonius2021-03-221-1/+1
| | | | | | | | | | | Physical port order watched from the back of the device is: 4 / 3 / 2 / 1 / WAN which also matches corresponding leds. This patch corrects LuCI switch webpage LAN port order. Signed-off-by: Walter Sonius <walterav1984@gmail.com> [improve commit title, fix sorting in 02_network] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 46c0634b508f731df487a7909c439b2794445e26)
* mvebu: add LED support for GL.iNet GL-MV1000Jeff Collins2021-03-222-1/+46
| | | | | | | | | This patch enables LED support for the GL.iNet GL-MV1000 Signed-off-by: Jeff Collins <jeffcollins9292@gmail.com> [add SPDX identifier on new file, add aliases, minor cosmetic issues] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> (cherry picked from commit 6e0c780eb3b4ba1e52216c1d671897749dd81829)
* bcm27xx: bcm2711: correctly disable HW_RANDOM_BCM2835Álvaro Fernández Rojas2021-03-221-0/+1
| | | | | | | | | It was removed in bac74aff5e36, but it should have been disabled. More info: https://forum.openwrt.org/t/make-image-stops-at-random-number-generator-bcm27xx/91429/7 Fixes: bac74aff5e36 ("bcm27xx: bcm2711: disable HW_RANDOM_BCM2835") Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com> (cherry picked from commit f93b544f01)
* archs38: Add CONFIG_HZ=100Hauke Mehrtens2021-03-191-0/+1
| | | | | | | | This kernel config option was missing and resulted in a question when building. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> (cherry picked from commit 047b7621bb3ac266d193cf110a468e42f844be4f)
* bcm53xx: backport first 5.13 DTS changesRafał Miłecki2021-03-173-1/+476
| | | | | | | | This adds NVMEM bindings that are needed for proper booting on Linksys devices. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 98d456a14e00e24acec36247fb5bd379da90f84e)
* bcm47xx: make WGT634U NVRAM patch apply againRafał Miłecki2021-03-171-19/+9
| | | | | | Fixes: 1c48eee5b2bc ("kernel: backport Broadcom NVRAM driver cleanups") Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 9530b9bb78845910de711d425f1e4b1c7d539b13)
* bcm53xx: initialize NVRAM from NVMEM driverRafał Miłecki2021-03-172-0/+92
| | | | | | | | | | | | NVRAM access may be needed early in boot process. Reading it using mtd happens quite late in the init process. Add NVRAM initialization to the NVMEM driver which comes up early and depends on IO mapping only. This is required by Linksys devices which use NVRAM content for proper partitioning (detecting current firmware partition). Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit baf04eed028a838518c65be48cbaabe0892343aa)
* kernel: backport Broadcom NVRAM driver cleanupsRafał Miłecki2021-03-175-0/+357
| | | | | | | Refactoring of bcm47xx_nvram driver. It's used by bcm47xx and bcm53xx. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 1c48eee5b2bcfaf9815cc9a6f6664392d17164cb)
* bcm53xx: backport NVMEM NVRAM driverRafał Miłecki2021-03-173-0/+181
| | | | | | | | It supports NVRAM access described using DT binding. Right now NVRAM data is exposed using /sys/bus/nvmem/ only. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 01b1b375281b77233d65eb0ebda8e4e3a1bd2407)
* bcm53xx: backport more upstream dts stuff from kernel 5.11Rafał Miłecki2021-03-177-0/+507
| | | | | Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 8078d89a5357d13dc3f2e2055fd9d663c4f1bd04)
* bcm53xx: group dts backports by upstream kernel versionRafał Miłecki2021-03-174-1/+6
| | | | | | | It's a simple renaming thing. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit d0ee398c36983ccb2ee514e71f10d3c274546f17)
* bcm4908: backport recent bcm_sf2 changesRafał Miłecki2021-03-177-8/+265
| | | | | | | One 5.12 link fix and 5.13 crossbar support. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit e1b4fd52a8efe1dfcad4f4fbe59f1c35a09be0bd)
* bcm4908: backport recent bcm4908_enet changesRafał Miłecki2021-03-174-0/+431
| | | | | | | This includes 5.12 fix and 5.13 improvements. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 7091e312307f4563d4a7afb5946140120cfa87fa)
* bcm4908: backport first PHY 5.13 patchesRafał Miłecki2021-03-172-3/+43
| | | | | | | | 1. Upstream accepted version of Kconfig change 2. Documentation binding fix Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit d7c8ca4d0b5c18c08e645f010fd0012f54c1c102)
* bcm4908: use accepted 5.13 DTS patchesRafał Miłecki2021-03-1712-50/+238
| | | | | | | | | | | | | Some patches were slightly cleaned up. One things worth mentioning is that adding: phy-mode = "rgmii" broke SF2 driver. It made it access random register breaking switch setup. That's why this commit also adds a quick sf2 fix. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 05dbfe616d551bce1a19d3846c8949c047325624)
* kernel: add pending mtd patches adding NVMEM supportRafał Miłecki2021-03-1710-11/+260
| | | | | | | | | It's meant to provide upstream support for mtd & NVMEM. It's required e.g. for reading MAC address from mtd partition content. It seems to be in a final shape so it's worth testing. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit e90e75b12c818c49704755b9e530491aee2d554c)
* kernel: move mtd ofpart accepted patchRafał Miłecki2021-03-171-0/+0
| | | | | | | Move upstream patch to the backport directory. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit deceb039931cd8eb011a0eb65731f335662070d0)
* bcm4908: prepare to support TP-Link Archer C2300 V1Rafał Miłecki2021-03-175-0/+239
| | | | | | | | | | | It's a BCM4906 based device (2 CPU cores). It has 512 MiB of RAM, 4 LAN ports, 1 WAN port, 2 USB ports, NAND flash. WiFi unknown at this point. Flashing is possible using CFE only, proper image will be worked on later. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 8d24da14702b8da820bf2e3952d5691f77136018)
* kernel: add the latest mtd patch extending ofpart parserRafał Miłecki2021-03-178-43/+41
| | | | | | | | | | | | | This adds the latest version of ofpart commit. It hopefully 1. Doesn't break compilation 2. Doesn't break partitioning (this time). It's required to implement fixed partitioning with some quirks. It's required by bcm53xx, bcm4908, kirkwood, lantiq and mvebu. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 7a7b2fd809809fbd7045bd3dad4fc896a6fef06f)
* bcm4908: backport Ethernet driver fixes from the 5.12Rafał Miłecki2021-03-174-2/+103
| | | | | | | The most noticeable one is fix for RX stopping on high traffic. Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit acbea54bc29a22d8fb171bc9da0f1b16fb0ec233)
* bcm4908: add bcm_sf2 fixes for the 5th GPHYRafał Miłecki2021-03-172-0/+76
| | | | | | | | This allows using the last integrated PHY (and so e.g. WAN port on the ASUS GT-AC5300). Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit ad8b759fd17bd31fdb7a026f247fd6ec81b372d3)
* build,ib: add STRIP_ABI option for manifestPaul Spooren2021-03-161-1/+2
| | | | | | | | | | | | | The ImageBuilder `make manifest` prints all installed packages. This function can be used to create a list of package and corresponding package versions before attempting image creation. When called with `--strip-abi` OPKG can automatically strip attached ABIVersions from package names. Make this function accessible for the ImageBuilder by adding a `STRIP_ABI` variable. Signed-off-by: Paul Spooren <mail@aparcar.org> (cherry picked from commit 0f7cd97f812adaf4b2c2048227610d150aec72cc)
* kernel: bump 5.4 to 5.4.105Hauke Mehrtens2021-03-1615-191/+15
| | | | | | | | | | | | | Refreshed all patches. The following patches were applied upstream: * 755-v5.8-net-dsa-add-GRO-support-via-gro_cells.patch * 831-v5.9-usbip-tools-fix-build-error-for-multiple-definition.patch Compile-tested on: x86_64, ipq40xx, ath79 Runtime-tested on: x86_64, ipq40xx, ath79 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ramips: rename mtk-hsdma to hsdma-mt7621Ilya Lipnitskiy2021-03-151-2/+2
| | | | | | | | | | | | | Follows upstream rename: https://lore.kernel.org/driverdev-devel/20210130034507.2115280-1-ilya.lipnitskiy@gmail.com/ Fixes ramips builds on 5.4.102 Cc: John Audia <graysky@archlinux.us> Cc: David Bauer <mail@david-bauer.net> Cc: Petr Štetiar <ynezz@true.cz> Signed-off-by: Ilya Lipnitskiy <ilya.lipnitskiy@gmail.com> (cherry picked from commit 58ad113087b3db7567507202b94d94756056a455)
* kernel: add compatibility with upstream threaded NAPI patchFelix Fietkau2021-03-141-6/+19
| | | | | | | | Enable threading if dev->threaded is set. This will be used to bring mt76 back in sync with upstream Signed-off-by: Felix Fietkau <nbd@nbd.name> (cherry-picked from commit 3d1ea0d77f9d)
* bcm63xx: AD1018-nor: add NAND flashDaniel González Cabanelas2021-03-081-0/+24
| | | | | | | | | | The Sercomm AD1018 has a NAND flash. We recently added support for NANDs in this target. Use the internal NAND as additional storage. Signed-off-by: Daniel González Cabanelas <dgcbueu@gmail.com> (cherry-picked from commit a48ef37747)
* kernel: bump 5.4 to 5.4.102Hauke Mehrtens2021-03-0640-80/+80
| | | | | | | | | Refreshed all patches. Compile-tested on: ath79, lantiq, ipq40xx, x86_64 Runtime-tested on: ipq40xx, x86_64 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* 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)
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 06:32:09 +0000