summaryrefslogtreecommitdiffstats
path: root/arch
Commit message (Collapse)AuthorAgeFilesLines
* ARM: Rockchip: Add rk3568 BananaPi R2 Pro board supportFrank Wunderlich2022-02-119-0/+736
| | | | | | | | | | | | | | | | | | This adds support for the BananaPi R2 Pro board. It is basicly a copy of rk3568 evb board but with slightly modified DTS. Added GPIO-Leds to dts and modified the hw-detection a bit. Tested features so far are: - 1st stage booting - Network - SD card and Emmc - usb (1.1 and 3 work, usb2 not working) - power LED (green) Signed-off-by: Frank Wunderlich <frank-w@public-files.de> Link: https://lore.barebox.org/20220211091354.11573-1-linux@fw-web.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: rockchip: rk3568-evb: Drop unused propertySascha Hauer2022-02-101-1/+0
| | | | | | | supports-sd is unused in barebox and there's no upstream binding for it. Remove this property. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* kvx: remove unused CONFIG_ARCHINFOMasahiro Yamada2022-02-081-7/+0
| | | | | | | | | | | This is defined, but not used anywhere. $ git grep ARCHINFO arch/kvx/Kconfig:config ARCHINFO Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Link: https://lore.barebox.org/20220207134743.1775403-1-masahiroy@kernel.org Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* sandbox: symlink stickypage.bin into build directoryAhmad Fatoum2022-02-071-0/+6
| | | | | | | | | | Sandbox will try to access a stickypage.bin in the same directory if possible. Instead of relying on users to copy it there, just create a symlink. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220207075604.1014259-1-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* ARM: rockchip-v8-defconfig: Enable USBSascha Hauer2022-01-251-2/+20
| | | | | | | The USB controllers on the rk3568 are supported, so enable them in the defconfig file. Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Merge branch 'for-next/spdx'Sascha Hauer2022-01-19920-29/+1805
|\
| * treewide: add SPDX-License-Identifier for files without explicit licenseAhmad Fatoum2022-01-051-0/+2
| | | | | | | | | | | | | | | | | | Record GPL-2.0-only as license for all files lacking an explicit license statement. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220103120539.1730644-12-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * arch: add SPDX-License-Identifier to all .c filesAhmad Fatoum2022-01-05148-2/+296
| | | | | | | | | | | | | | | | | | Record GPL-2.0-only as license for all files lacking an explicit license statement. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220103120539.1730644-11-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * arch: add SPDX-License-Identifier to all .S filesAhmad Fatoum2022-01-0539-6/+75
| | | | | | | | | | | | | | | | | | Record GPL-2.0-only as license for all files lacking an explicit license statement. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220103120539.1730644-10-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * arch: add SPDX-License-Identifier to all headersAhmad Fatoum2022-01-05263-10/+520
| | | | | | | | | | | | | | | | | | Record GPL-2.0-only as license for all files lacking an explicit license statement. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220103120539.1730644-9-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * ARM: i.MX: add SPDX-License-Identifier for DCDAhmad Fatoum2022-01-05159-2/+306
| | | | | | | | | | | | | | | | | | | | | | In absence of a license statement, the default is GPL-2.0-only. Add that to the DCD files. All of // /* */ # are acceptable comment characters in the DSL. If there are nearby comments in the file, the same character is used, otherwise #. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220103120539.1730644-8-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * treewide: add SPDX-License-Identifier for .gitignoreAhmad Fatoum2022-01-0514-0/+28
| | | | | | | | | | | | | | | | | | Makes the files not appear when searching for files that lack SPDX-License-Identifier. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220103120539.1730644-4-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * treewide: add SPDX-License-Identifier for Kbuild/KconfigAhmad Fatoum2022-01-05296-9/+578
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To verify only Kconfig/Makefile is touched: git show --numstat --format=oneline HEAD | grep -v 'Kconfig\|Makefile' will print only arch/powerpc/Kbuild. To verify nothing unexpected is added: git show -U0 | grep '^-[^-]\|^+[^+]' | sort -u Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220103120539.1730644-3-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | Merge branch 'for-next/riscv'Sascha Hauer2022-01-1918-107/+512
|\ \
| * | RISC-V: Virt: enable more useful optionsAhmad Fatoum2022-01-122-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | Incoming tutorial will showcase some barebox features, so enable them in the config for use. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220108171524.587144-9-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | RISC-V: add stacktrace support via frame pointer walkingAhmad Fatoum2022-01-127-6/+106
| | | | | | | | | | | | | | | | | | | | | | | | | | | Make debugging more convenient by implementing stack_dump() and changing exception handlers to print stack trace along with the register dump. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220108171524.587144-8-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | RISC-V: don't use x8/s0/fp in assemblyAhmad Fatoum2022-01-123-35/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | Free up the register to allow building a configuration with x8/s0 used as the frame pointer. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220108171524.587144-7-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | RISC-V: virt: riscvemu: clear frame buffer before jumping to reset vectorAhmad Fatoum2022-01-121-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Our poor man's reset just resumes execution at the reset vector, so the framebuffer will maintain its contents over reset, leading to artifacts. Clear screen before reset to avoid this. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220108171524.587144-6-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | RISC-V: virt: riscvemu: be explicit about HTIF base addressAhmad Fatoum2022-01-121-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The normal riscvemu console is Virt I/O, which isn't really suitable to poke from the command line as part of the incoming jsbarebox tutorial. The HTIF on the other hand can be poked quite comfortably. To make it look more like normal devices, fix up an address. No functional change. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220108171524.587144-5-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | RISC-V: virt: riscvemu: repurpose 64k low RAM for state/environmentAhmad Fatoum2022-01-125-0/+131
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TinyEMU's RISC-V machine emulates a 64K SRAM at address 0. First 4K page is unused, then a maximum of 0x40 bytes for boot ROM (trampoline that passes FDT), then the FDT. The remainder of the 64K is unused. Make use of that space for storing state and environment. We start the mtd-ram at 0x1000 to easily allow for a faulting zero page. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220108171524.587144-4-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | RISC-V: virt: riscvemu: add HTIF DEBUG_LL supportAhmad Fatoum2022-01-122-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Default console of riscvemu is available Virt I/O console and as a HTIF blocking character device. We already support Virt I/O console, but the HTIF is easier to support for very early low level debugging. Add DEBUG_LL support to facilitate using it. Note: when using a framebuffer, riscvemu doesn't allocate a default console, so barebox calling into HTIF will segfault the emulator. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220108171524.587144-3-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | power: reset: add RISC-V/UC Berkely HTIF poweroff driver supportAhmad Fatoum2022-01-124-15/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We already have a driver in board code and device tree passed by emulator already has a node for it. Match against it and create a proper driver. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220108171524.587144-2-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | RISC-V: virt: activate all consolesAhmad Fatoum2022-01-122-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While CONSOLE_ACTIVATE_NONE + stdout-path is usually the way to go, main console on this platform can be virtio console, which can't be referenced as is in DT, so just enable all consoles. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220108171524.587144-1-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | include: <asm/csr.h>: sync with upstreamAhmad Fatoum2022-01-101-52/+161
| | | | | | | | | | | | | | | | | | | | | | | | | | | We don't define CONFIG_RISCV_PRIV_1_9, so deleted stuff by the sync is unused anyway. No functional change. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220108171445.586681-1-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | Merge branch 'for-next/misc'Sascha Hauer2022-01-1921-180/+95
|\ \ \
| * | | ARM: mnt-reform: switch to deep-probeLucas Stach2022-01-181-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Now that all drivers used on this platform properly handle deep-probe, we can switch it on. Signed-off-by: Lucas Stach <dev@lynxeye.de> Link: https://lore.barebox.org/20220116213221.3466936-3-dev@lynxeye.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | ARM: rpi: set uart0-pl0110 clk to 48MHzOleksij Rempel2022-01-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At least on RPi2 this clock is 48MHz. This issue was not visible, becouse amba-pl011 driver was not reseting UART controller after changing baudrate. So, clk settings was not updated for some time. Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de> Link: https://lore.barebox.org/20220114082141.302151-2-o.rempel@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | clk: rockchip: extend for rk3399 supportAhmad Fatoum2022-01-171-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a very straight-forward port of Linux' clock driver for the SoC facilitated with the very convenient changes done to synchronize barebox clock framework with Linux'. It adds support for clock tree, restart handler and a reset controller. Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Link: https://lore.barebox.org/20220114083825.726347-3-ahmad@a3f.at Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | ARM64: rockchip: add config symbol for ARMv8-based rk3399 SoCAhmad Fatoum2022-01-175-1/+51
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As preperation for adding support for the RK3399-based Radxa Rock Pi N10, define the ARCH_RK3399 config symbol and associated boilerplate. Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Link: https://lore.barebox.org/20220114083825.726347-2-ahmad@a3f.at Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | ARM: rockchip: add new ARCH_ROCKCHIP_{V7,V8} symbolsAhmad Fatoum2022-01-142-8/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In preparation for adding rk3399 support, which is another SoC with ARMv8 CPUs, add new ARCH_ROCKCHIP_{V7,V8} symbols for the common functionality. Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Link: https://lore.barebox.org/20220114083825.726347-1-ahmad@a3f.at Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | ARM64: qemu-virt64: disable MMUAhmad Fatoum2022-01-101-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We have CFI flash at address 0 till start of RAM. Until we have a scheme to remap the flash, so it's usable at that address, just disable the MMU in the defconfig. Currently the defconfig prints a couple of error messages on every start up for cfi-flash as well as environment and state that depend on it. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220108171356.586099-2-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | x86: remove reference to empty fileAhmad Fatoum2022-01-051-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This might have been needed in the past when there was legacy boot machine support. Now there isn't, so we can just delete it. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220103115824.1725086-5-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | arm: mvebu: Replace license and copyright boilerplate by SPDX identifiersUwe Kleine-König2022-01-0311-166/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Converts the files that licensecheck can determine to be licensed under GPL-2.0-only or GPL-2.0-or-later and also convert their copyright statements to SPDX. Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Link: https://lore.barebox.org/20211230143145.68650-1-u.kleine-koenig@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | | Merge branch 'for-next/kvx'Sascha Hauer2022-01-197-53/+39
|\ \ \ \
| * | | | kvx: add kvx_sfr_field_valClement Leger2022-01-181-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add this macro for upcoming socinfo driver. This extract a sfr field using only its name. Signed-off-by: Clement Leger <clement.leger@bootlin.com> Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu> Link: https://lore.barebox.org/20220117221917.26970-10-jmaselbas@kalray.eu Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | kvx: enable FITIMAGE supportClement Leger2022-01-182-1/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enable FITIMAGE support in kvx defconfig and add code to handle fit boot from bootm command. This is rather a simple addition and it allow to boot a fit image containing an ELF file as the kernel. Signed-off-by: Clement Leger <clement.leger@bootlin.com> Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu> Link: https://lore.barebox.org/20220117221917.26970-6-jmaselbas@kalray.eu Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | kvx: Accept LINUX_BOOT_PARAM_MAGIC as a valid magic valueJules Maselbas2022-01-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Both defines FSBL_PARAM_MAGIC and LINUX_BOOT_PARAM_MAGIC have a similar uses and yet have different values. Making barebox accept both as valid magic boot param will make it possible to use qemu-system-kvx to boot a barebox image as a normal kernel. Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu> Link: https://lore.barebox.org/20220117221917.26970-4-jmaselbas@kalray.eu Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | kvx: Move LINUX_BOOT_PARAM_MAGIC in asm/common.hJules Maselbas2022-01-183-13/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Declare both defines FSBL_PARAM_MAGIC and LINUX_BOOT_PARAM_MAGIC in the same header file, as they both have a very similar uses and value. Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu> Link: https://lore.barebox.org/20220117221917.26970-3-jmaselbas@kalray.eu Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * | | | kvx: dma: Remove arch dma_map/unmap_singleJules Maselbas2022-01-181-38/+0
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since dma_map/unmap_single functions have been moved to common, barebox doesn't compile for kvx anymore. The original functions were doing some magic to support 32bits dma buffer addresses. The original behavior can be replaced by a device-tree dma-range property. Fixes: 3f975f810 ("dma: move dma_map/unmap_single from ARM to common code") Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu> Link: https://lore.barebox.org/20220117221917.26970-2-jmaselbas@kalray.eu Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | | ARM: rpi: use ENTRY_FUNCTION_WITHSTACK to prepare for ARM64 supportAhmad Fatoum2022-01-171-18/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | arm_setup_stack used in start_raspberry_pi is not safe on ARM64, due to lack of __naked support. since 76bced6fe146 ("ARM: document arm_setup_stack() pitfalls"), its use in ARM64 code is a compile-time error. The Raspberry Pi 4 support will be ARM64. To allow it to reuse the existing low-level code, use the new ENTRY_FUNCTION_WITHSTACK, which will set up stack appropriately for both ARM32 and ARM64. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220114084227.308804-3-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | | ARM: turn arm_mem_stack_top into a macroAhmad Fatoum2022-01-171-7/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This makes it possible to use for static initialization, like done in a follow-up commit. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220114084227.308804-2-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | | ARM: implement ENTRY_FUNCTION_WITHSTACKAhmad Fatoum2022-01-173-5/+49
|/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The point of ENTRY_FUNCTION is to write the entry point in C. Due to lack of __naked on ARM64, the start of the entry point will have prologue using stack and it's not possible to set up the stack safely without branching into non-inline assembly[0]. On ARM32, where we got __naked, we have the potential for a different problem: If BootROM sets up stack for us and we branch to a naked function, which doesn't set up its own stack, compiler may decide to spill local variables overwriting instructions it had already run[1]. For code reuse between ARM and ARM64, it would be nice to use the same entry point structure for both. Currently, the only way is to write it in non-inline assembly using the ENTRY_PROC macro. This introduces another way: the ARM64 barebox header has enough space for 8 instructions of which 5 are unused (2 instructions compiler prologue + 1 instruction to jump after the header), we could place a stack setup routine there to avoid having to write a separate assembly file. For ARM32, we just call arm_setup_stack and branch out directly after, freeing board porters of the burden of getting it right. Add a new ENTRY_FUNCTION_WITHSTACK to realize this. [0]: 76bced6fe146 ("ARM: document arm_setup_stack() pitfalls"), [1]: b51b15ba1738 ("RISC-V: board-dt-2nd: move low level init into nonnaked function") Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220114084227.308804-1-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | x86: <asm/io.h>: fix outl/outsl access sizeAhmad Fatoum2022-01-101-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | outl so far behaved like outb, probably due to a copy-paste error when it was first added. We have three users in-tree for outl: * drivers/serial/serial_ns16550_pci.c only for handling a Quatech qurik, which probably no one ever needed * drivers/serial/serial_ns16550.c For platform drivers with a 4 byte I/O port resource. Only possible user is x86 and that has a 1 byte I/O port resource. Thus no one used this either. * drivers/watchdog/itco_wdt.c Here it indeed triggers a bug, although in my testing the WDAT was functional without. Fix this up so new code doesn't have to track this down. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20220107063644.22595-1-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | | Revert "ARM: beaglebone: init MPU speed to 800Mhz"Ahmad Fatoum2022-01-071-1/+1
| |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Commit 130c7d6715e9 ("ARM: beaglebone: init MPU speed to 800Mhz") causes warm reboot from within Linux v5.14.0 to no longer succeed. barebox MLO is entered, but hangs. Reset from within barebox is unaffected. This can be reproduced using DistroKit 949c5ef2b9a6 ("v7a: barebox: version bump v2021.08.0 → v2021.11.0") on a Beaglebone Black. Until that's figured out, revert the commit; functional reboot is more important than the quicker boot up. This reverts commit 130c7d6715e932a1e0b3e026fea97f700ab33ea9. Fixes: 130c7d6715e9 ("ARM: beaglebone: init MPU speed to 800Mhz") Reported-by: arwie # IRC Cc: Marc Reilly <marc@cpdesign.com.au> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20211203185154.388145-1-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* | RISC-V: cpu: fix build with CONFIG_RISCV_EXCEPTIONS=nAhmad Fatoum2022-01-051-0/+2
|/ | | | | | | | | | | | Building without CONFIG_RISCV_EXCEPTIONS causes a compile error, because of a definition mismatch. data_abort_mask is a no-op without exception support, but interrupt.c defines it as a different type of symbol. Skip interrupt.c compilation to fix the build error. Reported-by: Yann Sionneau <ysionneau@kalray.eu> Signed-off-by: Ahmad Fatoum <ahmad@a3f.at> Link: https://lore.barebox.org/20211204130854.1624493-1-ahmad@a3f.at Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
* Merge branch 'for-next/x86'Sascha Hauer2021-12-156-26/+12
|\
| * x86_64: do not pass the EFI image handle or system table to relocationMasahiro Yamada2021-11-172-7/+3
| | | | | | | | | | | | | | | | | | | | | | | | The _reloc() function in reloc_x86_64.c is passed with the EFI image handle and system table, but they are unrelated to the relocation. In fact, they are not used at all. Remove them and clean up the assembler code as well. Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Link: https://lore.barebox.org/20211117034918.1226358-6-masahiroy@kernel.org Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * x86: reuse cmd_objcopy to generate barebox.efiMasahiro Yamada2021-11-171-6/+5
| | | | | | | | | | | | | | | | | | | | The objcopy rule is defined in scripts/Makefile.lib Reuse it. Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Link: https://lore.barebox.org/20211117034918.1226358-5-masahiroy@kernel.org Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * x86: stop copying unneeded sections to barebox.efiMasahiro Yamada2021-11-171-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Stop copying the following sections: __barebox_initcalls __barebox_exitcalls __barebox_cmd .barebox_magic Such sections do not exist. Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Link: https://lore.barebox.org/20211117034918.1226358-4-masahiroy@kernel.org Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
| * x86: remove x86-specific cmd_barebox__Masahiro Yamada2021-11-171-8/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | The difference from cmd_barebox__ in the top Makefile is: -shared -Bsymbolic -znocombreloc Put the flags to LDFLAGS_barebox, and remove the x86-specific cmd_barebox__. Signed-off-by: Masahiro Yamada <masahiroy@kernel.org> Link: https://lore.barebox.org/20211117034918.1226358-3-masahiroy@kernel.org Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>