aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/bcm63xx
Commit message (Collapse)AuthorAgeFilesLines
* bcm63xx: periph_intc: report effective affinityDaniel Gonzalez Cabanelas2020-05-141-0/+20
| | | | | | | | | | | The bcm6345-periph-intc driver only targets a single CPU at a time, even if the notional affinity is wider. Let's inform the core code about this. This patch gets rid of the kernel message: "genirq: irq_chip bcm6345-periph-intc did not update eff. affinity mask of irq 52" Signed-off-by: Daniel Gonzalez Cabanelas <dgcbueu@gmail.com>
* bcm63xx: ext_intc: fix warningÁlvaro Fernández Rojas2020-05-141-0/+28
| | | | | | | | | | | | | | | | | In file included from ./arch/mips/include/asm/io.h:34, from ./arch/mips/include/asm/mmiowb.h:5, from ./include/linux/spinlock.h:60, from ./include/linux/irq.h:14, from drivers/irqchip/irq-bcm6345-ext.c:10: drivers/irqchip/irq-bcm6345-ext.c: In function 'bcm6345_ext_intc_of_init': ./arch/mips/include/asm/mach-bcm63xx/ioremap.h:48:9: warning: 'base' may be used uninitialized in this function [-Wmaybe-uninitialized] return is_bcm63xx_internal_registers((unsigned long)addr); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/irqchip/irq-bcm6345-ext.c:255:16: note: 'base' was declared here void __iomem *base; ^~~~ Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: periph_intc: fix warningÁlvaro Fernández Rojas2020-05-141-0/+20
| | | | | | | | | drivers/irqchip/irq-bcm6345-periph.c: In function 'bcm6345_periph_irq_handle': drivers/irqchip/irq-bcm6345-periph.c:55:21: warning: 'block' may be used uninitialized in this function [-Wmaybe-uninitialized] struct intc_block *block; ^~~~~ Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: redboot: fix warningÁlvaro Fernández Rojas2020-05-141-1/+1
| | | | | | | | | drivers/mtd/parsers/redboot.c: In function 'parse_redboot_partitions': drivers/mtd/parsers/redboot.c:194:59: warning: suggest parentheses around '-' in operand of '&' [-Wparentheses] fis_origin = (buf[i].flash_base & (master->size << 1) - 1); ~~~~~~~~~~~~~~~~~~~~^~~ Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: bcm6362: fix pinctrl bugÁlvaro Fernández Rojas2020-05-141-0/+11
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: image: remove unused definitionÁlvaro Fernández Rojas2020-05-141-2/+1
| | | | | | KERNEL_ENTRY isn't used by lzma-loader. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: remove linux 4.14 supportÁlvaro Fernández Rojas2020-05-14192-23019/+0
| | | | Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: replace "ok" with "okay" for status in DTS filesAdrian Schmutzler2020-05-1289-185/+185
| | | | | | | While "ok" is recognized in DT parsing, only "okay" is actually mentioned as valid value. Replace it accordingly. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: use generic diag.shAdrian Schmutzler2020-05-1248-216/+377
| | | | | | | | | | | | | | | | This commit removes the target-specific diag.sh script. This way, the generic one is used for the target, which uses DT-aliases to specify the LEDs used. Though generic diag.sh allows to use different LEDs to indicate different states, this patch just moves the old assignment and does not try to "improve" the assignment by using additional colors. However, individual proposals to do so are welcome. For the few cases where status_led2 was used in old diag.sh, only the primary LED was migrated. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* kernel: bump 4.14 to 4.14.180Koen Vandeputte2020-05-122-3/+4
| | | | | | | | | | | | | Refreshed all patches. Fixes: - CVE-2020-12114 - CVE-2020-11669 Compile-tested on: pistachio Runtime-tested on: none Signed-off-by: Koen Vandeputte <koen.vandeputte@ncentric.com>
* bcm63xx: loader-lzma: use default lzmaÁlvaro Fernández Rojas2020-05-122-10/+6
| | | | | | Specific CFE LZMA parameters aren't needed for LZMA Loader. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: image: rename LOADADDR to KERNEL_LOADADDRÁlvaro Fernández Rojas2020-05-121-9/+8
| | | | | | Also remove KERNEL_ENTRY, since it's the same as KERNEL_LOADADDR Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* bcm63xx: switch to 5.4 kernelÁlvaro Fernández Rojas2020-04-181-2/+1
| | | | | | | Seems stable after 6 days of testing on some of my devices. Let's switch to 5.4 in order to get more feedback. Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
* kernel: remove non-existant symbolsAleksander Jan Bajkowski2020-04-131-2/+0
| | | | | | These symbols exist only in older kernels and can be removed. Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* bcm63xx: disable all devices with <= 4MiB flash and <= 32 MiB RAMJonas Gorski2020-04-121-0/+11
| | | | | | | | | | | Device with 4 MiB flash and 32 MiB RAM won't be able to run OpenWrt in a sufficient manner without tweaks, so don't build images for them by default. This includes all BCM6338, BCM6345 and BCM6348 "generic" devices, as there are no supported devices of these with more than that. Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
* bcm63xx: remove support for kernel 4.19Adrian Schmutzler2020-04-12177-21979/+0
| | | | | | | | | | Since stable kernel for this target is still 4.14, kernel 4.19 has never been used much (and actually was broken for some devices). So, since we bump testing kernel to 5.4, there is no real need to keep 4.19 and have an additional version to care about. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: use kernel 5.4 as testing kernelAdrian Schmutzler2020-04-121-1/+1
| | | | | | | | | This uses 5.4 as testing kernel. Since 4.19 has not seen broad testing yet, just keep 4.14 as stable kernel until 5.4 is ready. Tested on Comtrend AR-5387un (Thanks to @Noltari). Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: 5.4: fix compilation for changed driver_find_deviceAdrian Schmutzler2020-04-121-1/+5
| | | | | | | | | In kernel patch 92ce7e83b4e5 ("driver_find_device: Unify the match function with class_find_device()") the arguments of functions used with driver_find_device are adjusted. Do the same for our local user. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: 5.4: add removed helper syscon_regmap_lookup_by_pdevnameAdrian Schmutzler2020-04-121-0/+64
| | | | | | | | | | | The helper syscon_regmap_lookup_by_pdevname has been removed in kernel patch 29d14b668d2f ("mfd: Remove unused helper syscon_regmap_lookup_by_pdevname") due to lack of users. However, we use this function in our local pinctrl drivers for BCM6358 and BCM6368. Thus, we have to add it locally. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: prevent fall-through in kernel patches for 5.4Adrian Schmutzler2020-04-124-8/+11
| | | | | | | | | | | | | | | | | | | | | In kernel 5.4 -Werror=implicit-fallthrough is treated as error: arch/mips/bcm63xx/cpu.c: In function 'detect_cpu_clock': arch/mips/bcm63xx/cpu.c:158:2: error: this statement may fall through [-Werror=implicit-fallthrough=] { ^ arch/mips/bcm63xx/cpu.c:179:2: note: here case BCM6328_CPU_ID: ^~~~ cc1: all warnings being treated as errors This can be fixed by adding "Fall through" as a comment where intended, and has to be fixed by returning a proper default otherwise. In case of the default clock frequency for BCM6318 we fixed this by returning the default value taken from BCM6328 and BCM6362. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: fix missing watchdog core dependencyAdrian Schmutzler2020-04-121-0/+1
| | | | | | | | | | | | | | | | | This patch follows the other patches that added the watchdog core to various (armvirt, malta, ath79, ...) targets that have been hit by the following build error: Package kmod-hwmon-sch5627 is missing dependencies for the following libraries: watchdog.ko In theory, we could have just added the CONFIG_WATCHDOG_CORE=y to the Kconfig variable of kmod-hwmon-sch5627's package definition. This would have forced the watchdog core to be builtin and less architectures would need to be updated. But we might as well follow through here. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: update config for kernel 5.4Adrian Schmutzler2020-04-121-14/+24
| | | | | | Update config with make kernel_oldconfig. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: refresh patches for kernel 5.4Adrian Schmutzler2020-04-1239-718/+143
| | | | | | | | Refresh patches to make them apply to kernel 5.4. The removed patches have been merged upstream. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* bcm63xx: copy files to kernel 5.4Adrian Schmutzler2020-04-12177-0/+21974
| | | | | | | Copy config and patches to kernel 5.4. make kernel_oldconfig has been run on 4.19 beforehand. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: gather DEVICE_VARS into one placeSungbo Eo2020-03-211-5/+6
| | | | | | | | | | | Place DEVICE_VARS assignments at the top of the file or above Device/Default to make them easier to find. For ramips, remove redundant values already present in parent file. Signed-off-by: Sungbo Eo <mans0n@gorani.run> [do not touch ar71xx, extend commit message] Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
* treewide: remove maintainer variable from targetsPetr Štetiar2020-03-161-1/+0
| | | | | | | | | | | | | There is no such role as target maintainer anymore, one should always send corresponding changes for the review and anyone from the commiters is allowed to merge them or eventually use the hand break and NACK them. Lets make it clear, that it is solely a community doing the maintenance tasks. Signed-off-by: Petr Štetiar <ynezz@true.cz> Acked-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> Acked-by: Piotr Dymacz <pepe2k@gmail.com>
* kernel: remove non-existant symbols from 4.19 configAleksander Jan Bajkowski2020-02-221-4/+0
| | | | | | These symbols only exist in kernel version <= 4.15 Signed-off-by: Aleksander Jan Bajkowski <A.Bajkowski@stud.elka.pw.edu.pl>
* brcm63xx: rename target to bcm63xxAdrian Schmutzler2020-02-14501-0/+59298
This change makes the names of Broadcom targets consistent by using the common notation based on SoC/CPU ID (which is used internally anyway), bcmXXXX instead of brcmXXXX. This is even used for target TITLE in make menuconfig already, only the short target name used brcm so far. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-04 19:17:21 +0000