aboutsummaryrefslogtreecommitdiff
path: root/target/linux
Commit message (Collapse)AuthorAge
...
* ixp4xx: Add USRobotics USR8200 supportLinus Walleij2023-10-25
| | | | | | | This brings back USRobotics USR8200 support to the IXP4xx target. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* ixp4xx: Add a ixp4xx hardware crypto kernel moduleLinus Walleij2023-10-25
| | | | | | | | The IXP4xx crypto module must be loaded after the rootfs is up as it depends on loading some NPE microcode from the file system. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* ixp4xx: Resurrect IXP4xx support using device treeLinus Walleij2023-10-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This resurrects the support for IXP4xx using device tree rather than the old (deleted) board files. The final pieces of IXP4xx board files were deleted in Linux v5.19. Ext4 root filesystems on CF and USB are supported by the default config. We support these three initial targets: - The Gateworks Avila GW2348 reference design has 64MB of RAM and 32MB of flash and also supports USB and CompactFlash. - The Gateworks Cambria GW2358 reference design has 128MB of RAM and 32MB of flash and also supports USB and CompactFlash. - The old and stable Linksys NSLU2 works fine as well, albeit it only has 32MB of RAM so it has been marked as non-default. The 8MB of flash can only fit the kernel, so it has been patched to boot from exteral media on USB. I have used it successfully as a NAS with ksmbd and LUCI web API, see: https://dflund.se/~triad/krad/ixp4xx/ Signed-off-by: Howard Harte <hharte@magicandroidapps.com> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> Reviewed-by: Tomasz Maciej Nowak <tmn505@gmail.com>
* generic: Support Altima AMI101L PHYLinus Walleij2023-10-25
| | | | | | | | This is a backport of the patch to support the Altima AMI101L PHY which is merged for the v6.7 kernel. This PHY is used in the IXP4xx-based USRobotics USR8200. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* generic: RTC7301 byte-addressed IOLinus Walleij2023-10-25
| | | | | | | | This is a backport of the patch for byte addressed IO to the Epson RTC7301 driver. This is used by the IXP4xx-based USRobotics USR8200. Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
* sifiveu: remove 5.15 supportZoltan HERPAI2023-10-24
| | | | | | With 6.1 as the default kernel, there is no reason to keep 5.15 around. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* sifiveu: switch to kernel v6.1Zoltan HERPAI2023-10-24
| | | | | | Enable kernel v6.1 as the default kernel for sifiveu. Signed-off-by: Zoltan HERPAI <wigyori@uid0.hu>
* bcm53xx: disable unused switch ports in downstream patchRafał Miłecki2023-10-24
| | | | | | | | This makes Linux use correct switch ports again. Fixes: a4792d79e899 ("bcm53xx: backport DT changes from v6.5") Fixes: https://github.com/openwrt/openwrt/issues/13548 Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: backport DT changes queued for v6.7Rafał Miłecki2023-10-24
| | | | | | | | Among other changes this commit makes Linux use correct switch ports again. Fixes: a4792d79e899 ("bcm53xx: backport DT changes from v6.5") Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* bcm53xx: simplify patch adding switch portsRafał Miłecki2023-10-24
| | | | | | | We now have all raw ports defined in bcm-ns.dtsi. Leave only lables in custom device files. Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* kernel: ath79, bmips: refresh 5.15 patchesMarek Behún2023-10-23
| | | | | | | One LED patch for ath79 and one LED patch for bmips need to be refreshed. Signed-off-by: Marek Behún <kabel@kernel.org>
* kernel: 5.15: Backport Turris Omnia LED patchesMarek Behún2023-10-23
| | | | | | | | | | | | | | | | | | | | | This backports patches leds: turris-omnia: convert to use dev_groups leds: turris-omnia: Use sysfs_emit() instead of sprintf() leds: turris-omnia: Drop unnecessary mutex locking leds: turris-omnia: Do not use SMBUS calls leds: turris-omnia: Make set_brightness() more efficient leds: turris-omnia: Support HW controlled mode via private trigger leds: turris-omnia: Add support for enabling/disabling HW gamma correction leds: turris-omnia: Fix brightness setting and trigger activating into backport-5.15. The above patches replace: leds: turris-omnia: support HW controlled mode via private trigger leds: turris-omnia: initialize multi-intensity to full leds: turris-omnia: change max brightness from 255 to 1 from mvebu/patches-5.15. Signed-off-by: Marek Behún <kabel@kernel.org>
* bcm53xx: update patch fixing NVMEM driver for NVRAMRafał Miłecki2023-10-23
| | | | | | | 1. Avoid corrupting (replacing '=' with '\0') NVRAM content 2. Check actual NVRAM data length to avoid allocating huge buffers Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
* Revert "lantiq: xrx200: mark subtarget as source-only"Hauke Mehrtens2023-10-23
| | | | | | | | | | | | | | | | | | | This reverts commit 0c117e1f6ccbee684ea0589d9024ca9dec4679c9. Activate the lantiq/xrx200 target again. There are still some problems with the GSWIP, but it is not leaking packets to the wrong bridge in normal operations. It shows some error messages at configuration like these: [ 54.308861] gswip 1e108000.switch: port 5 failed to add ce:9d:84:d1:81:f0 vid 1 to fdb: -22 [ 54.325633] gswip 1e108000.switch: port 5 failed to add e8:de:27:95:c1:b4 vid 0 to fdb: -22 [ 54.351242] gswip 1e108000.switch: port 5 failed to add e8:de:27:95:c1:b4 vid 1 to fdb: -22 [ 54.358311] gswip 1e108000.switch: port 5 failed to delete ce:9d:84:d1:81:f0 vid 1 from fdb: -2 The problems are described in this pull request: https://github.com/openwrt/openwrt/pull/13200 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* bcm53xx: Linksys EA9200 nvram and 02_network fixesRani Hod2023-10-22
| | | | | | | | | | 1) clear nvram partialboots upon successful boot This behavior is already defined for EA9500; enabled for EA9200 too. 2) fix MAC address in board.d/02_network Use the correct nvram variable to derive lan/wan MAC address. Signed-off-by: Rani Hod <rani.hod@gmail.com>
* ramips: TP-link archer A6/C6 device tree updatesRani Hod2023-10-22
| | | | | | | | | | | | | | | | Set correct GPIO (10) for the WPS button. This matches GPIO settings in vendor GPL sources. Note that GPL sources also mention a USB indicator LED (GPIO 13) but the device has neither an external USB port nor a USB LED. In addition, prefixes (button-, led-) are added to relevant DT entries, as well as color and function specifications for LEDs. Closes: #13736 Reported-by: Waldemar Czabaj <kaball@wp.pl> Signed-off-by: Rani Hod <rani.hod@gmail.com> (added led mitigations for wifi leds) Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* kernel: bump 6.1 to 6.1.59John Audia2023-10-21
| | | | | | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.59 Manually rebased: bcm27xx/patches-6.1/950-0124-Add-support-for-all-the-downstream-rpi-sound-card-dr.patch Removed upstreamed: generic/backport-6.1/781-v6.6-02-net-dsa-qca8k-fix-potential-MDIO-bus-conflict-when-a.patch[1] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.59&id=881050b25b1dda7b0f14d40d1b09bf38cb3b427c Build system: x86/64 Build-tested: x86/64/AMD Cezanne Run-tested: x86/64/AMD Cezanne Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: bump 6.1 to 6.1.58John Audia2023-10-21
| | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.58 All patches automatically rebased. Signed-off-by: John Audia <therealgraysky@proton.me>
* kernel: 6.1: Backport Turris Omnia LED patchesMarek Mojík2023-10-20
| | | | | | | | | | | | | | | | | | | | This backports patches leds: turris-omnia: Use sysfs_emit() instead of sprintf() leds: turris-omnia: Drop unnecessary mutex locking leds: turris-omnia: Do not use SMBUS calls leds: turris-omnia: Make set_brightness() more efficient leds: turris-omnia: Support HW controlled mode via private trigger leds: turris-omnia: Add support for enabling/disabling HW gamma correction leds: turris-omnia: Fix brightness setting and trigger activating into backport-6.1. The above patches replace: leds: turris-omnia: support HW controlled mode via private trigger leds: turris-omnia: initialize multi-intensity to full leds: turris-omnia: change max brightness from 255 to 1 from mvebu/patches-6.1. Signed-off-by: Marek Mojík <marek.mojik@nic.cz>
* realtek: add support for TP-Link T1600G-28TS v3Andreas Böhler2023-10-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is an RTL8382-based switch with 24 copper ports + 4 SFP ports Specifications: --------------- * SoC: Realtek RTL8382M * Flash: 32 MiB SPI flash * RAM: 256 MiB * Ethernet: 24x 10/100/1000 Mbps * Buttons: 1x "Reset" button * UART: 1x serial header, unpopulated * SFP: 4 SFP ports Works: ------ - (24) RJ-45 ethernet ports - Switch functions - Buttons - Sys LED on front panel (no port LEDs) Not yet enabled: ---------------- - Port LEDs (no driver for RTL8231 in this mode) - SFP cages (no driver for PHY) Install via web interface: ------------------------- Not supported at this time. Install via serial console/tftp: -------------------------------- The U-Boot firmware drops to a TP-Link specific "BOOTUTIL" shell at 38400 baud. There is no known way to exit out of this shell, and no way to do anything useful. Ideally, one would trick the bootloader into flashing the sysupgrade image first. However, if the image exceeds 6MiB in size, it will not work. To install OpenWRT: Prepare a tftp server with: 1. server address: 192.168.0.146 2. the image as: "uImage.img" Power on device, and stop boot by pressing any key. Once the shell is active: 1. Ground out the CLK (pin 16) of the ROM (U6) 2. Select option "3. Start" 3. Bootloader notes that "The kernel has been damaged!" 4. Release CLK as soon as bootloader thinks image is corrupted. 5. Bootloader enters automatic recovery -- details printed on console 6. Watch as the bootloader flashes and boots OpenWRT. Blind install via tftp: ----------------------- This method works when it's not feasible to install a serial header. Prepare a tftp server with: 1. server address: 192.168.0.146 2. the image as: "uImage.img" 3. Watch network traffic (tcpdump or wireshark works) 4. Power on the device. 5. Wait 1-2 seconds then ground out the CLK (pin 16) of the ROM (U6) 6. When 192.168.0.30 makes tftp requests, release pin 16 7. Wait 2-3 minutes for device to auto-flash and boot OpenWRT Signed-off-by: Andreas Böhler <dev@aboehler.at>
* ipq40xx: wpj428: switch to zimage to fit kernel partitionLeon M. Busch-George2023-10-20
| | | | | | | | | | | | | | | Like with some other ipq40xx devices, the kernel image size for the WPJ428 is limited in stock u-boot. For that reason, the current release doesn't include an image for the board. By switching to the zImage format, the kernel image size is reduced which re-enables the build process. The image boots and behaved normally through a few days of testing. Before the switch to kernel version 6.1, it was possible to reduce the image size by enough when disabling UBIFS and its otherwise unneeded dependencies. Signed-off-by: Leon M. Busch-George <leon@georgemail.eu>
* apm821xx: WNDR4700: fix broken sysupgrade, factory imagesChristian Lamparter2023-10-20
| | | | | | | | | | | | | | | | | | prepend-dtb got extended to handle the Meraki devices too, the problem here was that the Netgear WNDR4700 expects an u-boot header in front of the DTB, whereas Meraki devices don't. Since the header was dropped, the WNDR4700's uboot started to complain: Bad Magic Number,it is forbidden to be written to flash!! when flashing the factory.img since it expects an u-boot header there. Fixes: 5dece2d9355a ("apm821xx: switch over from DTB_SIZE to DEVICE_DTC_FLAGS") Reported-by: @kisgezenguz Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ath79: AP105: use fixed layout cell "mac-base"Christian Lamparter2023-10-20
| | | | | | This drops a use of the deprecated "mac-address-increment". Signed-off-by: Christian Lamparter <chunkeey@gmail.com>
* ipq40xx: switch to performance governor by defaultKoen Vandeputte2023-10-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Doing a simple ping to my device shows this: 64 bytes from 10.0.253.101: icmp_seq=1 ttl=64 time=2.00 ms 64 bytes from 10.0.253.101: icmp_seq=2 ttl=64 time=2.02 ms 64 bytes from 10.0.253.101: icmp_seq=3 ttl=64 time=1.68 ms 64 bytes from 10.0.253.101: icmp_seq=4 ttl=64 time=1.91 ms 64 bytes from 10.0.253.101: icmp_seq=5 ttl=64 time=1.92 ms 64 bytes from 10.0.253.101: icmp_seq=6 ttl=64 time=2.04 ms Some users even report higher values on older kernels: 64 bytes from 192.168.1.10: seq=0 ttl=64 time=0.612 ms 64 bytes from 192.168.1.10: seq=1 ttl=64 time=2.852 ms 64 bytes from 192.168.1.10: seq=2 ttl=64 time=2.719 ms 64 bytes from 192.168.1.10: seq=3 ttl=64 time=2.741 ms 64 bytes from 192.168.1.10: seq=4 ttl=64 time=2.808 ms The problem is that the governor is set to Ondemand, which causes the CPU to clock all the way down to 48MHz in some cases. Switching to performance governor: 64 bytes from 10.0.253.101: icmp_seq=1 ttl=64 time=0.528 ms 64 bytes from 10.0.253.101: icmp_seq=2 ttl=64 time=0.561 ms 64 bytes from 10.0.253.101: icmp_seq=3 ttl=64 time=0.633 ms 64 bytes from 10.0.253.101: icmp_seq=4 ttl=64 time=0.526 ms In theory, using the Performance governor should increase power draw, but it looks like it really does not matter for this soc. Using a calibrated precision DC power supply (cpu idle): Ondemand 24.00V * 0.134A = 3.216 Watts 48.00V * 0.096A = 4.608 Watts Performance 24.00V * 0.135A = 3.240 Watts 48.00V * 0.096A = 4.608 Watts Let's simply switch to the Performance governor by default to fix the general jittery behaviour on devices using this soc. Tested on: MikroTik wAP ac Fixes: #13649 Reviewed-by: Robert Marko <robimarko@gmail.com> Reviewed-by: Thibaut VARÈNE <hacks@slashdirt.org> Signed-off-by: Koen Vandeputte <koen.vandeputte@citymesh.com>
* armsr: preserve configuration during sysupgradeChristian Buschau2023-10-20
| | | | | | | | | | Copy configuration to boot partition (partition 1) instead of root partition (partition 2) because the root partition is not writable if it's a suqashfs image. Move configuration back to root during preinit. Fixes: https://github.com/openwrt/openwrt/issues/13695 Signed-off-by: Christian Buschau <cbuschau@d00t.de>
* layerscape: kernel: refresh 6.1 patchesPawel Dembicki2023-10-19
| | | | | | Kernel patches copied from 5.15 need to be refreshed. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* generic: kernel: add missing symbolPawel Dembicki2023-10-19
| | | | | | It was found during work on layerscape target. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: port "-Werror" fix from NXP treePawel Dembicki2023-10-19
| | | | | | | | | | | | | | | | At this moment, 702-phy-Add-2.5G-SGMII-interface-mode.patch cause error durring kernel compilation: CC drivers/net/phy/phylink.o drivers/net/phy/phylink.c: In function 'phylink_get_capabilities': drivers/net/phy/phylink.c:443:9: error: enumeration value 'PHY_INTERFACE_MODE_2500SGMII' not handled in switch [-Werror=switch] 443 | switch (interface) { | ^~~~~~ cc1: all warnings being treated as errors NXP take care of it. Let's port their patch. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: add 6.1 kernel as testingPawel Dembicki2023-10-18
| | | | | | It allow to test 6.1 kernel in Layerscape. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: 6.1: refresh kernel configPawel Dembicki2023-10-18
| | | | | | Done by 'make kernel_oldconfig'. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: copy config 5.15 to 6.1Pawel Dembicki2023-10-18
| | | | | | Configs was just copied. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: refresh kernel configPawel Dembicki2023-10-18
| | | | | | Done by 'make kernel_oldconfig'. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* layerscape: copy patches 5.15 to 6.1Pawel Dembicki2023-10-18
| | | | | | | | | | | | Patches recreated from NXP 6.1 tree: 400-LF-20-3-mtd-spi-nor-Use-1-bit-mode-of-spansion-s25fs.patch 701-staging-add-fsl_ppfe-driver.patch 702-phy-Add-2.5G-SGMII-interface-mode.patch Patch 703 includes changes made by Christian Marangi, extracted from commit 0d4a547905d4. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
* Revert "ramips: convert MT7915 EEPROM to NVMEM format"Shiji Yang2023-10-17
| | | | | | | | | | | | | | | | Some MT7915 devices need to load the second part of the eeprom to work properly. The mt76 driver is not yet ready to read the pre-cal data via the NVMEM cell. Therefore, partially revert commit to fix the device probe issue on some devices. P.S. Except for D-Link and Ubnt devices, It is still uncertain whether pre-cal data is required for other devices in the patch. This partially reverts commit 9ac891f8c44124e931c15f1257347cd8ba311a19. Fixes: https://github.com/openwrt/openwrt/issues/13700 Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: add missing mt76 packages for Telco Electronics X1Shiji Yang2023-10-17
| | | | | | | | Telco Electronics X1 has MT7603E and MT7612E PCIe NICs. They are driven by kmod-mt7603 and kmod-mt76x2. Ref: 73e0f52b6e4e ("ramips: add support for Telco Electronics X1") Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: fix factory partition size for SNR-CPE-W4NShiji Yang2023-10-17
| | | | | | | | | The starting address of 'factory' partition is 0x40000, and the starting address of the next partition is 0x50000. It's obvious that the correct size for the 'factory' is 0x10000, just like other MT7620 devices. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: fix frequency limit property for some Edimax devicesShiji Yang2023-10-17
| | | | | | | | These three devices uses MT7612E PCIe NIC and supported by the 'mt76' driver. So the right frequency limit property should be `ieee80211-freq-limit`. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: remove useless status property from wmac dts nodeShiji Yang2023-10-17
| | | | | | | | On the ramips target, all 'wmac' nodes in SoC dtsi are enabled by default except mt7628. There is no need to mark them as 'okay' again. So these useless properties can be removed. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: convert mt76 PCIe NIC EEPROM to NVMEM format for legacy SoCsShiji Yang2023-10-17
| | | | | | | | | | This patch converts MT761{0,2,3} PCIe WiFi calibration data to NVMEM format for legacy Ralink SoCs (MT7620 and Mt7628). The EEPROM size of the MT7610 and MT7612 is 0x200. there are only three devices uses MT7613 NIC, ASUS RT-AC1200 V2, COMFAST CF-WR758AC V2 and Keenetic KN-1613. The EEPROM size of them is 0x4da8. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: convert MT7628 EEPROM to NVMEM formatShiji Yang2023-10-17
| | | | | | | This patch converts MT7628 WiFi calibration data to NVMEM format. The EEPROM size is 0x400. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: convert rt2x00 EEPROM to NVMEM formatShiji Yang2023-10-17
| | | | | | | This patch converts legacy Ralink SoCs and MT7620 WiFi calibration data to NVMEM format. The EEPROM size is 0x200. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: fix mtd partition node names for Phicomm PSG1208Shiji Yang2023-10-17
| | | | | | | | The mtd partition node name should be "partition@${offset}". However, the offsets of the PSG1208 don't match the partition 'reg' properties. This patch correct the wrong offsets. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: fix DTS EEPROM property for some MT7628 devicesShiji Yang2023-10-17
| | | | | | | The MT7628 integrated wireless is driven by `mt76`, so the right EEPROM property name is `mediatek,mtd-eeprom`. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* ramips: convert the remaining mtd-mac-address to NVMEM formatShiji Yang2023-10-17
| | | | | | | | `mtd-mac-address` has been abandoned. Therefore, convert them to NVMEM format. This patch also removes some useless mtd-mac-address properties. Signed-off-by: Shiji Yang <yangshiji66@qq.com>
* qualcommax: ipq8074: use upstreamed CPUFreq NVMEM supportRobert Marko2023-10-16
| | | | | | | | | | IPQ8074 CPUFreq NVMEM support has finally landed upstream, so lets use the upstreamed version. This has a benefit of also supporting IPQ8174 (Oak) family for which SMEM SoC ID-s were also upstreamed. Signed-off-by: Robert Marko <robimarko@gmail.com>
* lantiq: update binding for ralink EEPROM swapChristian Marangi2023-10-16
| | | | | | | | | Binding for ralink EEPROM swap changed from ralink,mtd-eeprom-swap to ralink,eeprom-swap. Update every entry. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
* ramips: fix ZyXEL NR7101 bricking typoBjørn Mork2023-10-15
| | | | | | | | | | A typo snuck in with the addition of Cudy M1800, changing "nr7101" to "nt7101". The result is a default network config for NR7101 without the only ethernet interface on the NR7101, thereby soft bricking it. Fixes: f6d394e9f2fd ("ramips: add support for Cudy M1800") Signed-off-by: Bjørn Mork <bjorn@mork.no>
* qualcommax: add pending GPLL parent fixesRobert Marko2023-10-15
| | | | | | | | | | | | | | | | | | | | SBL will configure IPQ807x cores to boot at 800MHz as a safe default frequency that is provided by GPLL0, but GPLL0 is not currently configured as a possible parent in the APSS clock driver not being passed to it via DTS which will then cause the kernel to not properly identify the current CPU frequency during booting and will think that CPU is currently at XO frequency of 19.2MHz instead of 800MHz cores are actually at and print: cpufreq: cpufreq_online: CPU0: Running at unlisted initial frequency: 19200 KHz, changing to: 1017600 KHz So, lets import patches pending upstream to prevent GPLL scaling and feed the GPLL0 clock to APSS clock driver so we get: cpufreq: cpufreq_online: CPU0: Running at unlisted initial frequency: 800000 KHz, changing to: 1017600 KHz This is mostly cosmetic fix, but with all of the possible SBL and FW versions there could be edge cases resolved by this and not scaling GPLL-s anymore. Signed-off-by: Robert Marko <robimarko@gmail.com>
* kernel: bump 6.1 to 6.1.57John Audia2023-10-14
| | | | | | | | | | | | | | | | | | | | | Changelog: https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.57 Manually rebased: generic/pending-6.1/702-net-ethernet-mtk_eth_soc-enable-threaded-NAPI.patch Removed upstreamed: qualcommax/patches-6.1/0134-PCI-qcom-Fixing-broken-pcie-enumeration-for-2_3_3-co.patch[1] All other patches automatically rebased. 1. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.1.57&id=2dfb5f324d799f4545e17631415aba6d302a8e2b Build system: x86/64 Build-tested: x86/64/AMD Cezanne Run-tested: x86/64/AMD Cezanne Reviewed-by: Robert Marko <robimarko@gmail.com> Signed-off-by: John Audia <therealgraysky@proton.me>
* config-6.1: disable CONFIG_ARM64_ERRATUM_2966298John Audia2023-10-14
| | | | | | | | Disable new ksym globally as OpenWrt does not have any targets that use A520 cores. Reviewed-by: Robert Marko <robimarko@gmail.com> Signed-off-by: John Audia <therealgraysky@proton.me>
Powered by cgit, Themed by Ted Yin.