aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* mvebu/cortexa72: enable armv8-CE crypto algosEneas U de Queiroz2022-06-041-0/+11
| | | | | | | | | | | This enables armv8 crypto extensions version of AES, GHASH, SHA1, SHA256, and SHA512 algorithms in the kernel. The choice of algorithms match the 32-bit versions that are enabled in the target config-5.10 file, but were only used by the cortexa9 subtarget. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* mvebu/cortexa72: refresh kernel 5.10 configEneas U de Queiroz2022-06-041-1/+3
| | | | | | This is result of a plain make kernel_oldconfig CONFIG_TARGET=subtarget. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* mvebu/cortexa53: enable armv8-CE crypto algosEneas U de Queiroz2022-06-041-0/+11
| | | | | | | | | | | This enables armv8 crypto extensions version of AES, GHASH, SHA1, SHA256, and SHA512 algorithms in the kernel. The choice of algorithms match the 32-bit versions that are enabled in the target config-5.10 file, but were only used by the cortexa9 subtarget. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* mvebu/cortexa53: refresh kernel 5.10 configEneas U de Queiroz2022-06-041-1/+6
| | | | | | This is result of a plain make kernel_oldconfig CONFIG_TARGET=subtarget. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* layerscape/armv8_64b: enable armv8-CE crypto algosEneas U de Queiroz2022-06-041-0/+11
| | | | | | | This enables armv8 crypto extensions version of AES, GHASH, SHA256 and CRC T10 algorithms in the kernel. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* bcm4908: enable armv8-CE crypto algorithmsEneas U de Queiroz2022-06-041-0/+8
| | | | | | | This enables armv8 crypto extensions version of AES and GHASH algorithms in the kernel. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* bcm27xx/bcm2711: enable asm crypto algorithmsEneas U de Queiroz2022-06-041-0/+8
| | | | | | | | This enables arm64/neon version of AES, SHA256 and SHA512 algorithms in the kernel. bcm2711 does not support armv8 crypto extensions, so they are not included. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* bcm27xx/bcm2710: enable asm crypto algorithmsEneas U de Queiroz2022-06-041-0/+8
| | | | | | | | This enables arm64/neon version of AES, SHA256 and SHA512 algorithms in the kernel. bcm2710 does not support armv8 crypto extensions, so they are not included. Signed-off-by: Eneas U de Queiroz <cotequeiroz@gmail.com>
* ramips: use hotplug script for EAP615-Wall MACsStijn Tintel2022-06-032-2/+4
| | | | | | | | | | | | | Using nvmem-cells to set the MAC address for a DBDC device results in both PHY devices using the same MAC address. This in turn will result in multiple BSSes using the same BSSID, which can cause various problems. Use the hotplug script for the EAP615-Wall instead to avoid this. Fixes: a1b8a4d7b3ff ("ramips: support TP-Link EAP615-Wall") Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> Tested-by: Stijn Segers <foss@volatilesystems.org> Tested-By: Andrew Powers-Holmes <aholmes@omnom.net>
* kernel: fix crashes in bridge offload codeFelix Fietkau2022-06-022-10/+10
| | | | | | - fix an issues when accessing the port pointer of an expired/invalid fdb entry Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ipq40xx: add Aruba AP-365 specific BDFDavid Bauer2022-06-022-1/+10
| | | | | | | | | | | | | Aruba deploys a BDF in the root filesystem, however this matches the one used for the DK04 reference board. The board-specific BDFs are built into the kernel. The AP-365 shows sinificant degraded performance with increased range when used with the reference BDF. Replace the BDF with the one extracted from Arubas kernel. Signed-off-by: David Bauer <mail@david-bauer.net>
* kernel: add two ksyms to the generic kconfigsRui Salvaterra2022-06-012-0/+4
| | | | | | These will be prompted for with GCC 12. Signed-off-by: Rui Salvaterra <rsalvaterra@gmail.com>
* generic: 5.15: fix panic on tcp_no_window_check set with interface upChristian 'Ansuel' Marangi2022-05-291-39/+43
| | | | | | | | | | | The current reworked version cause kernel panic when the value is changes and an interface is up. Following the tcp_be_liberal impelementation, reimplement this to permit a safe change of this value without any panic. This has been tested with a QSDK package where tcp_no_window_check is used. Fixes: 92fb51bc9881 ("generic: 5.15: standardize tcp_no_window_check pending patch") Signed-off-by: Christian 'Ansuel' Marangi <ansuelsmth@gmail.com>
* realtek: don't unmask non-maskable GPIO IRQsSander Vanheule2022-05-301-0/+29
| | | | | | | | | | | | | | | | On uniprocessor builds, for_each_cpu(cpu, mask) will assume 'mask' always contains exactly one CPU, and ignore the actual mask contents. This causes the loop to run, even when it shouldn't on an empty mask, and tries to access an uninitialised pointer. Fix this by wrapping the loop in a cpumask_empty() check, to ensure it will not run on uniprocessor builds if the CPU mask is empty. Fixes: af6cd37f42f3 ("realtek: replace RTL93xx GPIO patches") Reported-by: INAGAKI Hiroshi <musashino.open@gmail.com> Reported-by: Robert Marko <robimarko@gmail.com> Tested-by: Robert Marko <robimarko@gmail.com> Signed-off-by: Sander Vanheule <sander@svanheule.net>
* ath79: fix label MAC address for D-Link DIR-825B1Sebastian Schaper2022-05-291-0/+1
| | | | | | | The label MAC address for DIR-825 Rev. B1 is the WAN address located at 0xffb4 in `caldata`, which equals LAN MAC at 0xffa0 incremented by 1. Signed-off-by: Sebastian Schaper <openwrt@sebastianschaper.net>
* ramips: disable unsupported background-radarDavid Bauer2022-05-292-0/+6
| | | | | | | | The UniFi 6 Lite as well as the Tenbay T-MB5EU do not have the third background-radar chain. For the Tenbay, the connector is present, however no antenna is connected to it. Signed-off-by: David Bauer <mail@david-bauer.net>
* malta: use default OpenWrt network configurationHauke Mehrtens2022-05-281-13/+0
| | | | | | | | | | | | | | | | Currently malta configures the first Ethernet device as WAN interface. If it finds a second one it will configure it as LAN. This commit reverses it to match armvirt and x86. If there is only one network device it will be configured as LAN device now. If we find two network devices the 2. one will be WAN. If no board.d network configuration is given it will be configured in package/base-files/files/etc/board.d/99-default_network Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> [minor typos] Signed-off-by: Paul Spooren <mail@aparcar.org>
* kernel: backport flow offload fixesRitaro Takenaka2022-05-274-2/+200
| | | | | | | | | Some dst in IPv6 flow offload table become invalid after the table is created. So check_dst is needed in packet path. Signed-off-by: Ritaro Takenaka <ritarot634@gmail.com> [Add patch for kernel 5.15 too and rename file] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ipq40xx: cut ath10k board file for mikrotik subtargetJohn Thomson2022-05-274-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Avoid shipping ath10k board file in Mikrotik initram images Most will only ever need to use these initram images once—to initially load OpenWrt, but fix these images for more consistent Wi-Fi performance between the initram and installed squashfs images. OpenWrt BUILDBOT config ignores -cut packages in the initram images build. This results in BUILDBOT initram images including the linux-firmware qca4019 board-2.bin, and (initram image booted) Mikrotik devices loading a generic BDF, rather than the intended BDF data loaded from NOR as an api 1 board_file. buildbot snapshot booted as initram image: cat /etc/openwrt_version r19679-810eac8c7f dmesg | grep ath10k | grep -E board\|BDF [ 9.794556] ath10k_ahb a000000.wifi: Loading BDF type 0 [ 9.807192] ath10k_ahb a000000.wifi: board_file api 2 bmi_id 0:16 crc32 11892f9b [ 12.457105] ath10k_ahb a800000.wifi: Loading BDF type 0 [ 12.464945] ath10k_ahb a800000.wifi: board_file api 2 bmi_id 0:17 crc32 11892f9b CC: Robert Marko <robimarko@gmail.com> Fixes: 5eee67a72fed ("ipq40xx: mikrotik: dont include ath10k-board-qca4019 by default") Signed-off-by: John Thomson <git@johnthomson.fastmail.com.au> Reviewed-by: Robert Marko <robimarko@gmail.com>
* bmips: dgnd3700v2: fix network configÁlvaro Fernández Rojas2022-05-231-0/+1
| | | | | | | ucidef_set_bridge_device is needed for DGND3700v2 network config since VLAN 1 must be used for the switch to be correctly configured. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: add pwm-fan dependency to RPi PoEÁlvaro Fernández Rojas2022-05-221-1/+1
| | | | | | This is needed for the fan in the PoE hat to work. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* realtek: replace RTL93xx GPIO patchesSander Vanheule2022-05-224-64/+234
| | | | | | | | | | | Patches to support the SoC's GPIO controller for RTL930x and RTL931x devices have been accepted upstream. Replace the current preliminary patch with the upstream ones, excluding devictree binding changes. The updated patches add GPIO IRQ balancing support on RTL930x, but this cannot be used until these devices also support SMP. Signed-off-by: Sander Vanheule <sander@svanheule.net>
* mediatek: mt7622: add support for ELECOM WRC-X3200GST3INAGAKI Hiroshi2022-05-214-5/+464
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ELECOM WRC-X3200GST3 is a 2.4/5 GHz band 11ax (Wi-Fi 6) router, based on MT7622B. Specifications: - SoC : MediaTek MT7622B - RAM : DDR3 512 MiB (Nanya NT5CC256M16ER-EK) - Flash : SPI-NAND 128 MiB (Winbond W25N01GVZEIG) - WLAN : 2.4/5 GHz 4T4R - 2.4 GHz : MediaTek MT7622B (SoC) - 5 GHz : MediaTek MT7915A - Ethernet : 5x 10/100/1000 Mbps - Switch : MediaTek MT7531 - LEDs/Keys : 6x/4x (2x buttons, 1x slide-switch) - UART : through-hole on PCB - J19: 3.3V, GND, TX, RX from power jack side - 115200n8 - Power : 12 VDC, 1.5 A Flash instruction using factory image: 1. Boot WRC-X3200GST3 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:77 (Factory, 0x7FFF4 (hex)) WAN : 04:AB:18:xx:xx:78 (Factory, 0x7FFFA (hex)) 2.4 GHz: 04:AB:18:xx:xx:79 (Factory, 0x4 (hex)) 5 GHz : 04:AB:18:xx:xx:7A (none) Note: - currently, there is no "phy1tpt" trigger for 5 GHz wlan (MT7915) in "trigger" file of LEDs, use "phy1radio" trigger instead Signed-off-by: INAGAKI Hiroshi <musashino.open@gmail.com>
* ath79: NanoBeam M5 fix target_devicesJan-Niklas Burfeind2022-05-212-2/+2
| | | | | | | | | | Update the name of for the Ubiquiti NanoBeam M5 to match the auto-generated one at runtime. Otherwise sysupgrade complains about mismatching device names. This also required renaming the DTS. Signed-off-by: Jan-Niklas Burfeind <git@aiyionpri.me>
* ath79: add support for Ubiquiti NanoBeam M5Jan-Niklas Burfeind2022-05-212-0/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ubiquiti NanoBeam M5 devices are CPE equipment for customer locations with one Ethernet port and a 5 GHz 300Mbps wireless interface. Specificatons: - Atheros AR9342 - 535 MHz CPU - 64 MB RAM - 8 MB Flash - 1x 10/100 Mbps Ethernet with passive PoE input (24 V) - 6 LEDs of which four are rssi - 1 reset button - UART (4-pin) header on PCB Notes: The device was supported by OpenWrt in ar71xx. Flash instructions (web/ssh/tftp): Loading the image via ssh vias a stock firmware prior "AirOS 5.6". Downgrading stock is possible. * Flashing is possible via AirOS software update page: The "factory" ROM image is recognized as non-native and then installed correctly. AirOS warns to better be familiar with the recovery procedure. * Flashing can be done via ssh, which is becoming difficult due to legacy keyexchange methods. This is an exempary ssh-config: KexAlgorithms +diffie-hellman-group1-sha1 HostKeyAlgorithms ssh-rsa PubkeyAcceptedKeyTypes ssh-rsa User ubnt The password is ubnt. Connecting via IPv6 link local worked best for me. 1. scp the factory image to /tmp 2. fwupdate.real -m /tmp/firmware_image_file.bin -d * Alternatively tftp is possible: 1. Configure PC with static IP 192.168.1.2/24. 2. Enter the rescue mode. Power off the device, push the reset button on the device (or the PoE) and keep it pressed. Power on the device, while still pushing the reset button. 3. When all the leds blink at the same time, release the reset button. 4. Upload the firmware image file via TFTP: tftp 192.168.1.20 tftp> bin tftp> trace Packet tracing on. tftp> put firmware_image.bin Signed-off-by: Jan-Niklas Burfeind <git@aiyionpri.me>
* ath79: add support for MikroTik hAP (RB951Ui-2nD)Maciej Krüger2022-05-216-0/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The MikroTik hAP (product code RB951Ui-2nD) is an indoor 2.4Ghz AP with a 2 dBi integrated antenna built around the Atheros QCA9531 SoC. Specifications: - SoC: Atheros QCA9531 - RAM: 64 MB - Storage: 16 MB NOR - Winbond 25Q128FVSG - Wireless: Atheros QCA9530 (SoC) 802.11b/g/n 2x2 - Ethernet: Atheros AR934X switch, 5x 10/100 ports, 10-28 V passive PoE in port 1, 500 mA PoE out on port 5 - 8 user-controllable LEDs: · 1x power (green) · 1x user (green) · 4x LAN status (green) · 1x WAN status (green) · 1x PoE power status (red) See https://mikrotik.com/product/RB951Ui-2nD for more details. Notes: The device was already supported in the ar71xx target. Flashing: TFTP boot initramfs image and then perform sysupgrade. Follow common MikroTik procedure as in https://openwrt.org/toh/mikrotik/common. Signed-off-by: Maciej Krüger <mkg20001@gmail.com>
* ath79: add support for MikroTik RouterBOARD hAP ac liteThibaut VARÈNE2022-05-217-0/+142
| | | | | | | | | | | | | | | | | | | | | | | | | | | The MikroTik RB952Ui-5ac2nD (sold as hAP ac lite) is an indoor 2.4Ghz and 5GHz AP/router with a 2 dBi integrated antenna. See https://mikrotik.com/product/RB952Ui-5ac2nD for more details. Specifications: - SoC: QCA9533 - RAM: 64MB - Storage: 16MB NOR - Wireless: QCA9533 802.11b/g/n 2x2 / QCA9887 802.11a/n/ac 2x2 - Ethernet: AR934X switch, 5x 10/100 ports, 10-28 V passive PoE in port 1, 500 mA PoE out on port 5 - 6 user-controllable LEDs: - 1x user (green) - 5x port status (green) Flashing: TFTP boot initramfs image and then perform sysupgrade. The "Internet" port (port number 1) must be used to upload the TFTP image, then connect to any other port to access the OpenWRT system. Follow common MikroTik procedure as in https://openwrt.org/toh/mikrotik/common. Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>
* bcm27xx: sound-soc-rpi-cirrus: fix packageÁlvaro Fernández Rojas2022-05-201-2/+4
| | | | | | Fix kmod-sound-soc-rpi-cirrus package dependencies. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: add linux v5.15 supportÁlvaro Fernández Rojas2022-05-20133-0/+20886
| | | | | | | | Build system: x86_64 Build-tested: generic, smp Run-tested: generic/AR-5387un, smp/VR-3032u Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: modules: video: fix whitespaceÁlvaro Fernández Rojas2022-05-201-1/+1
| | | | | | No idea how this ended up here v2... Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: enable PWM drivers in configÁlvaro Fernández Rojas2022-05-205-18/+18
| | | | | | Removes PWM module package. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: rework ARCH_HAS_SYNC_DMA_FOR_CPU_ALL patchÁlvaro Fernández Rojas2022-05-201-25/+39
| | | | | | Let's disable ARCH_HAS_SYNC_DMA_FOR_CPU_ALL only for BCM6358. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: remove linux 5.10 compatibilityÁlvaro Fernández Rojas2022-05-2062-9491/+0
| | | | | | | A devent amount of patches have been upstreamed, so maintaining linux 5.10 on this target makes no sense. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: switch to linux 5.15Álvaro Fernández Rojas2022-05-201-2/+1
| | | | | | | I tested it locally and I couldn't find any regressions, so let's give this a wider test :). Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bmips: add linux v5.15 supportÁlvaro Fernández Rojas2022-05-2026-4/+1894
| | | | | | | | Build system: x86_64 Build-tested: generic, nand Run-tested: generic/AR-5387un, nand/VR-3032u Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: base-files: align network filesÁlvaro Fernández Rojas2022-05-192-4/+6
| | | | | | | | - Use the same order for /etc/board.d/02_network and /lib/preinit/05_set_preinit_iface_brcm2708. - Add missing RPi 400 and CM4 to /lib/preinit/05_set_preinit_iface_brcm2708. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: diag.sh: fix whitespaceÁlvaro Fernández Rojas2022-05-191-1/+1
| | | | | | No idea how this ended up here... Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ipq40xx: mikrotik: dont include ath10k-board-qca4019 by defaultRobert Marko2022-05-191-0/+1
| | | | | | | | | | | Since MikroTik subtarget now uses dynamic BDF loading its crucial that it doesnt include the board-2.bin at all which is provided by the ath10k-board-qca4019 package. So to resolve this dont include the ath10k-board-qca4019 package on the MikroTik subtarget. Signed-off-by: Robert Marko <robimarko@gmail.com>
* ipq-wifi: remove packaged BDF-s for MikroTik devicesRobert Marko2022-05-191-6/+4
| | | | | | | | | | | Since we now provide the BDF-s for MikroTik IPQ40xx devices on the fly, there is noneed to include package and ship them like we do now. This also resolves the performance issues that happen as MikroTik changes the boards and ships them under the same revision but they actually ship with and require a different BDF. Signed-off-by: Robert Marko <robimarko@gmail.com>
* ipq40xx: mikrotik: provide BDF-s on demandRobert Marko2022-05-191-0/+23
| | | | | | | | | | | Since we now can pass the API 1 BDF-s aka board.bin to the ath10k driver per radio lets use that to provide the BDF-s for MikroTik devices. This also resolves the performance issues that happen as MikroTik changes the boards and ships them under the same revision but they actually ship with and require a different BDF. Signed-off-by: Robert Marko <robimarko@gmail.com>
* config: limit CONFIG_DEBUG_INFO to top-level generic configsTony Ambardar2022-05-1818-19/+0
| | | | | | | | | | Remove redundant target-level entries, noting that these settings will be configured from "Kernel build options" of Kconfig. Signed-off-by: Tony Ambardar <itugrok@yahoo.com> Signed-off-by: Felix Fietkau <nbd@nbd.name> [remove from new configs introduced after patch submission] Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: add DEBUG_INFO_REDUCED config optionStijn Tintel2022-05-182-2/+0
| | | | | | | | Add DEBUG_INFO_REDUCED as a kernel config option and remove it from the kernel configs. This is in preparation of the upcoming option to enable BTF typeinfo, which is incompatible with DEBUG_INFO_REDUCED. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* layerscape/armv8_64b: enable DEBUG_INFO_REDUCEDStijn Tintel2022-05-181-1/+0
| | | | | | | | | | | | | We currently enable DEBUG_INFO_REDUCED for all targets via the generic kernel config. There is only one subtarget, layerscape/armv8_64b, that overrides this setting. As there is no explanation for this in the commit message that introduced this, and question to its author went unanswered, let's simply drop this symbol from the subtarget config. This way, we have consistency across the tree, and we do not have to introduce a special case when moving this symbol to an OpenWrt kernel config option. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* kernel: backport build fix for tools/resolve_btfidsStijn Tintel2022-05-182-0/+108
| | | | | | | Building tools/resolve_btfids requires libelf and zlib. Without this build fix, the kernel build system will not find these dependencies. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
* bcm27xx: add CPU_FREQ_GOV_SCHEDUTILJohn Audia2022-05-173-0/+7
| | | | | | | | | This is enabled upstream for bcm2709, bcm2710 and bcm2711. https://github.com/raspberrypi/linux/blob/dff79e31c3b05a50f725442c1fc19a6194491523/arch/arm/configs/bcm2709_defconfig#L51 https://github.com/raspberrypi/linux/blob/dff79e31c3b05a50f725442c1fc19a6194491523/arch/arm/configs/bcm2711_defconfig#L51 Signed-off-by: John Audia <graysky@archlinux.us> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: remove linux 5.10 configsÁlvaro Fernández Rojas2022-05-174-1721/+0
| | | | | | Sorry, I missed these when removing linux v5.10 support... Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: remove linux 5.10 compatibilityÁlvaro Fernández Rojas2022-05-17718-220355/+2
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: switch to 5.15Álvaro Fernández Rojas2022-05-171-2/+1
| | | | | | | I tested it locally and I couldn't find any regressions, so let's give this a wider test :). Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm27xx: add support for linux v5.15Álvaro Fernández Rojas2022-05-17924-1/+265734
| | | | | | | | | Build system: x86_64 Build-tested: bcm2708, bcm2709, bcm2710, bcm2711 Run-tested: bcm2708/RPiB+, bcm2709/RPi3B, bcm2710/RPi3B, bcm2711/RPi4B Signed-off-by: Marty Jones <mj8263788@gmail.com> Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: Add missing devm_regulator_get_exclusive()Hauke Mehrtens2022-05-171-0/+79
| | | | | | | | | | | This backports a patch from Linux 5.10.116 to fix a compile problem introduced in 5.10.114. drivers/usb/phy/phy-generic.c could not find devm_regulator_get_exclusive(). Fixes: 8592df67f40b ("kernel: bump 5.10 to 5.10.114") Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 14:57:40 +0000