aboutsummaryrefslogtreecommitdiffstats
path: root/target
Commit message (Collapse)AuthorAgeFilesLines
* brcm2708: image: stop using mkknlimg scriptÁlvaro Fernández Rojas2019-12-281-6/+1
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: switch to upstream cpufreq driverÁlvaro Fernández Rojas2019-12-283-5/+14
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* Revert "kernel: fix kmemleak warnings introduced in 305-mips_module_reloc.patch"Felix Fietkau2019-12-272-18/+12
| | | | | | This reverts commit a03afef7f2e8ae363a97357ec75ffbfef372a9ea. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ipq806x: build DEVICE_DTS based on SOC and device nameAdrian Schmutzler2019-12-271-11/+16
| | | | | | | | | | | | | | | | | | | | This patch uses the SOC variable to calculate DTS names automatically based on the SOC and the device definition node name. This reduces redundancy and (by having to choose DTS name appropriately) will unify the naming of a device in different places (image/Makefile, DTS name, compatible, image name). This is supposed to make life easier for developers and reviewers. Since the kernel uses a "soc-device.dts" scheme for this target, we use this for the derivation of DEVICE_DTS, too, leaving the DTS names unchanged for this target. Note that for some devices the kernel itself uses inconsistent names (DTS naming scheme vs. compatible), leaving us with a manual overwrite of DEVICE_DTS for those cases. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ipq40xx: build DEVICE_DTS based on SOC and device nameAdrian Schmutzler2019-12-2715-41/+42
| | | | | | | | | | | | | | | | | | | This patch uses the SOC variable to calculate DTS names automatically based on the SOC and the device definition node name. This reduces redundancy and (by having to choose DTS name appropriately) will unify the naming of a device in different places (image/Makefile, DTS name, compatible, image name). This is supposed to make life easier for developers and reviewers. Since the kernel uses a "soc-device.dts" scheme for this target, we use this for the derivation of DEVICE_DTS, too, and rename the files not having followed it so far. Note that for some devices the kernel itself is inconsistent, leaving us with a manual overwrite for ap.dk01.1-c1 and ap.dk04.1-c1. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* ramips: remove bogus ralink,mtd-eeprom with offset 0x4Adrian Schmutzler2019-12-277-8/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Several devices in mt76x8 subtarget use the following line to set up wmac in their DTS(I) files: ralink,mtd-eeprom = <&factory 0x4> This is strange for several reasons: - They should use mediatek,mtd-eeprom on this SOC - The caldata is supposed to start at 0x0 - The parent DTSI mt7628an.dtsi specifies mediatek,mtd-eeprom anyway, starting from 0x0 - The offset coincides with the default location of the MAC address in caldata Based on the comment in b28e94d4bfa1 ("ramips: MiWiFi Nano fixes"), it looks like the author for this device wanted to actually use mtd-mac-address instead of ralink,mtd-eeprom. A check on the same device revealed that actually the MAC address start at offset 4 there, so the correct caldata offset is 0x0. Based on these findings, and the fact that the expected location on this SOC is 0x0, we remove the "ralink,mtd-eeprom = <&factory 0x4>" statement from all devices in ramips (being only mt7628an anyway). Thanks to Sungbo Eo for finding and researching this. Reported-by: Sungbo Eo <mans0n@gorani.run> Fixes: b28e94d4bfa1 ("ramips: MiWiFi Nano fixes") Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: fix kmemleak warnings introduced in 305-mips_module_reloc.patchFelix Fietkau2019-12-272-12/+18
| | | | | | | Physically allocated memory for modules needs to be registered with kmemleak, so it can track it as object. Signed-off-by: Felix Fietkau <nbd@nbd.name>
* ipq40xx: use ath10k-ct-smallbuffers for 128 MiB devicesPaul Fertser2019-12-261-1/+3
| | | | Signed-off-by: Paul Fertser <fercerpav@gmail.com>
* ipq806x: fix wrong definition for tsense calibAnsuel Smith2019-12-261-2/+2
| | | | | | | | | We have only 11 sensors on ipq806x. Fix the reg property to load the right amount of data instead of the entire space. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: rework ipq806x specific tsense temp driverAnsuel Smith2019-12-261-0/+107
| | | | | | | | | | | | | | | | | | | | | | | | | | | Tsense driver for ipq806x have various problem. - Emit wrong error. On probing of this driver, nvmem driver can be not ready and this cause a EDEFER error. Actually this is not an error as the kernel will retry to probe the driver after the nvmem driver is loaded. - Use uninitialized value on trigger of critical temp - Doesn't free allocated memory Because of this, rework the driver and improve it by removing extra load of data. Change the logic of loading data. Use the backup calib data only when the calib data is not present. As the calibration is only needed to set the temp offset, we don't really need to read both calib data and set the offset based only on the backup one. Also change how the notifier function work. At times when we output the trigger message, we already have read the temp so remove the extra read and the wrong uninitialized data that probably caused a kernel panic for null pointer exception. (Think we never experience this bug because the router never reached that temp ever... So just lucky) Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: update kernel config with new driverAnsuel Smith2019-12-261-1/+1
| | | | | | | The config name for cpufreq driver has changed. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: refresh new and changed patchesAnsuel Smith2019-12-269-212/+496
| | | | | | | Refresh patches to remove fuzz Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq8065: update dtsi with new opp tableAnsuel Smith2019-12-261-53/+91
| | | | | | | | The new driver use opp table to register frequency. Drop psv bindings as they are not used anymore. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq8064: update dtsi with new opp tableAnsuel Smith2019-12-261-44/+80
| | | | | | | | | The new driver use opp table to register frequency. Drop psv bindings as they are not used anymore. Adds speedbin definition for nvmem driver Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: add patch to support krait cpu scaling driverAnsuel Smith2019-12-261-0/+351
| | | | | | | | | | This patch has been proposed but never actually merged to mainline. It was accepted but never re proposed by the creator. Rework it, fix kernel panic cause by double kfree. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: backport qcom-cpufreq-kryo patchAnsuel Smith2019-12-263-0/+551
| | | | | | | | Backport patch applied to qcom-cpufreq-kryo driver as krait cpu will base on this driver. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: drop old cpufreq patchAnsuel Smith2019-12-263-399/+0
| | | | | | | | Drop old cpufreq as now we have new driver that can use normal kernel opp definition Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: opp/core: update patch updating voltage tolerance on voltage adjustAnsuel Smith2019-12-261-12/+21
| | | | | | | | | | | Rework 0052-PM-OPP-Update-the-voltage-tolerance-when-adjusting-t to reflect changes upstream. - Skip unnecessary allocation of buffer to set u_volt - Change opp u_volt directly Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: opp/core: update patch allowing adjusting of OPP voltages at runtimeAnsuel Smith2019-12-261-61/+71
| | | | | | | | Update 0049-PM-OPP-Support-adjusting-OPP-voltages-at-runtime with upstream version. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ipq806x: fix bug in L2 cache scalingAnsuel Smith2019-12-261-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It has been notice a buf in L2 cache scaling where the scaling is not done proprely if the frequency is set to the initial state before the new frequency. From: https://patchwork.kernel.org/patch/10565443/ * The clocks are set to aux clock rate first to make sure the * secondary mux is not sourcing off of QSB. The rate is then set to * two different rates to force a HFPLL reinit under all * circumstances. In the initial stage of boot to force a new frequency to apply, is needed to first set the frequency back to the lowest one (aux_rate) and then to the target one. This force and make sure the controller actually switch the frequency to the right one. Apply the same mechanism to L2 frequency scaling. Before scaling to the target frequency, first set the frequency to the aux_rate to force the transition, then scale it to the target frequency. Doing the wrong way can produce unexpected results and could lock the scaling mechanism until a full reboot is done (Causing a full reset by the krait-cc driver) From: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=77612720a2362230af726baa4149c40ec7a7fb05 When the Hfplls are reprogrammed during the rate change, the primary muxes which are sourced from the same hfpll for higher frequencies, needs to be switched to the 'safe secondary mux' as the parent for that small window. This is done by registering a clk notifier for the muxes and switching to the safe parent in the PRE_RATE_CHANGE notifier and back to the original parent in the POST_RATE_CHANGE notifier. This should apply also to L2 scaling... as we can't relly use the notifier, we manually do this on L2 scaling. Tested-by: Stefan Lippers-Hollmann <s.l-h@gmx.de> [nbg6817/ipq8065] Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>
* ath79: tp-link: use ath10k-ct-smallbuffers for 64 MiB devicesPaul Fertser2019-12-251-5/+6
| | | | Signed-off-by: Paul Fertser <fercerpav@gmail.com>
* brcm2708: fix malformed patchÁlvaro Fernández Rojas2019-12-251-2/+2
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: update to latest patches from RPi FoundationÁlvaro Fernández Rojas2019-12-24803-2031/+8999
| | | | | | Also removes reverted patches. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* brcm2708: organize kernel patchesÁlvaro Fernández Rojas2019-12-241372-95751/+95751
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: bump 4.9 to 4.9.207Hauke Mehrtens2019-12-2422-47/+47
| | | | | | | | | Refreshed all patches. Compile-tested on: ar7 Runtime-tested on: none Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.14 to 4.14.160Hauke Mehrtens2019-12-2410-16/+16
| | | | | | | | | Refreshed all patches. Compile-tested on: ipq40xx, apm821xx Runtime-tested on: ipq40xx Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.19 to 4.19.91Hauke Mehrtens2019-12-2411-22/+22
| | | | | | | | | Refreshed all patches. Compile-tested on: ipq40xx, apm821xx Runtime-tested on: ipq40xx Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.19 to 4.19.90Koen Vandeputte2019-12-2434-386/+153
| | | | | | | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 010-dmaengine-dw-dmac-implement-dma-prot.patch - 950-0148-Increase-firmware-call-buffer-size-to-48-bytes.patch - 950-0206-Mailbox-firmware-calls-now-use-kmalloc-2749.patch - 402-leds-trigger-netdev-fix-handling-on-interface-rename.patch Fixes: - CVE-2019-19332 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com> [Add 010-dt-bindings-dmaengine-dw-dmac-add-protection-control.patch] Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* kernel: bump 4.14 to 4.14.159Koen Vandeputte2019-12-2443-268/+140
| | | | | | | | | | | | | | | Refreshed all patches. Remove upstreamed: - 302-0002-dmaengine-dw-implement-per-channel-protection-contro.patch Fixes: - CVE-2019-19332 Compile-tested on: cns3xxx Runtime-tested on: cns3xxx Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* ath79: use ath10k-ct-smallbuffers for 64 MiB devicesPaul Fertser2019-12-243-14/+14
| | | | Signed-off-by: Paul Fertser <fercerpav@gmail.com>
* treewide: Remove self from MAINTAINER entriesFlorian Fainelli2019-12-234-5/+1
| | | | Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
* kernel: Deactivate CONFIG_SFP in generic configHauke Mehrtens2019-12-235-4/+1
| | | | | | | | Deactivate CONFIG_SFP for kernel 4.19 in the generic configuration. The CONFIG_SFP configuration option was not set to anything in the ath79 build for me, set it to deactivated by default. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* ath79: Do not build dlink_dir-615-e4 by defaultHauke Mehrtens2019-12-231-0/+1
| | | | | | | The factory image for the dlink_dir-615-e4 is getting too big which makes the full ath79 tiny build fail, deactivate it by default. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* brcm2708: remove unneeded patchesÁlvaro Fernández Rojas2019-12-2383-183652/+3
| | | | | | | - wireless patches - defconfig patches Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* ramips: add label MAC address for Mikrotik RB750Gr3Sven Roederer2019-12-231-3/+1
| | | | | | | | | | | | The device label contains: E01: 74:4D:28:xx:xx:30 E05: 74:4D:28:xx:xx:34 The first value corresponds to the address set in hard_config 0x10. That one is taken for the label MAC address. Signed-off-by: Sven Roederer <freifunk@it-solutions.geroedel.de>
* ramips: simplify state_default/pinctrl0 in device DTS filesAdrian Schmutzler2019-12-23295-1941/+1355
| | | | | | | | | The node pinctrl0 is already set up in the SOC DTSI files, but defined again as member of pinctrl in most of the device DTS(I) files. This patch removes this redundancy for the entire ramips target. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* build: build proper VMDK formats for ESXI 6.5John Sommerville2019-12-231-0/+6
| | | | | | | | | | | | | | | | | | | | | VMWare ESXI 6.5 and above is not compatible with subformat=monolithicSparse (The default qemu-img convert -O VMDK option). Monolithic Sparse vmdk can be imported, but issues occur when running sysupgrade with new images and other tasks that modify the file system (issues like Kernel panics, reboot loops, sometimes crashing the Host ESXI box). This change creates an additional VMDK output file for ESXI that sets the subformat to monlithicFlat, and the adapter_type to the SCSI lsilogic controller. This change existed back on: 25e36d379e73d64d6316fae9dc841c5ef28980f1 But it looks like the change was removed when refactoring occurred with: 5f6a2732f892b6229473576d89cc963ae9c97d5d Signed-off-by: John Sommerville <jsommerville@untangle.com>
* lantiq: enable 5ghz wifi on VR200/VR200vKevin Schmidt2019-12-232-3/+22
| | | | | | Enable mt76 driver on VR200/VR200v. Signed-off-by: Kevin Schmidt <kevin.patrick.schmidt@googlemail.com>
* lantiq: fix phys ledAleksander Jan Bajkowski2019-12-231-2/+2
| | | | | | | | led2l and led2h value is incorrectly set by led3l and led3h. Bug was introduced in commit: 863e79f8d5544a8a884375d7e867f350fddca9b9 Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl> Fixes: 863e79f8d554 ("lantiq: add support for kernel 4.9")
* ramips: fix MAC address setup for Xiaomi MiWiFi NanoSungbo Eo2019-12-222-2/+2
| | | | | | | | MAC addresses are stored in factory partition at: 0x0004: WiFi 2.4GHz (label_mac +1) 0x0028: LAN, WAN (label_mac) Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* ramips: further improve support for Xiaomi MiWiFi NanoSungbo Eo2019-12-221-15/+13
| | | | | | | | | | | | | | | | | This patch does the following: - prepend vendor name to model - set status LEDs to follow the behavior in stock FW - simplify state_default node definition - use generic name for flash node Stock FW status indicators: https://files.xiaomi-mi.com/files/Mi_Router_Wi-Fi_Nano/Mi_router-NANO_EN.pdf > Yellow: power on / off > Blue: during normal operation > Red: in case of problems with the operation of the device Signed-off-by: Sungbo Eo <mans0n@gorani.run>
* lantiq: move include to parent falcon_lantiq_easy98000.dtsiAdrian Schmutzler2019-12-224-6/+2
| | | | | | | This moves the include of lantiq.dtsi from the DTS files to the parent falcon_lantiq_easy98000.dtsi. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: remove ar9_lantiq_easy50810.dtsAdrian Schmutzler2019-12-221-73/+0
| | | | | | This file seems to be orphaned, no device setup existing for it. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: use soc_vendor_device scheme on DTS fileAdrian Schmutzler2019-12-2290-99/+98
| | | | | | | | | | | | This renames lantiq DTS(I) files to follow soc_vendor_device scheme. This will make DTS files easier to maintain. As a side effect, DTS file name can be derived from device node names now, only having to specify a SOC variable in Makefiles. While at it, move files to arch/mips/boot/dts/lantiq subfolder. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: split device definitions into filesAdrian Schmutzler2019-12-227-851/+838
| | | | | | | This splits device definitions into several *.mk files to increase overview. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* lantiq: dts: assign the ASC pins to the serial controller nodeMartin Blumenstingl2019-12-223-8/+9
| | | | | | | | Assign the ASC pins to the serial controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the PCI pins to the PCI controller nodeMartin Blumenstingl2019-12-2227-260/+213
| | | | | | | | Assign the PCI pins to the PCI controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the STP pins to the STP GPIO controller nodeMartin Blumenstingl2019-12-2211-68/+36
| | | | | | | | Assign the STP pins to the STP GPIO controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the GPHY LED pins to the Ethernet controller nodeMartin Blumenstingl2019-12-227-54/+71
| | | | | | | | Assign the GPHY LED pins to the Ethernet controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
* lantiq: dts: assign the NAND pins to the nand-controller nodeMartin Blumenstingl2019-12-2216-85/+112
| | | | | | | | | | | | Assign the NAND pins to the NAND controller node instead of using pin hogging (where pins are assigned to the pin controller). This is the preferred way of assigning pins upstream. While here, define all NAND pins (CLE, ALE, read/RD, ready busy/RDY and CE/CS1). This means that the pinctrl subsystem knows that these pins are in use and cannot be re-assigned as GPIOs for example. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-08 08:11:02 +0000