u-boot.git/arch/m68k/cpu/mcf52x2, branch master

m68k: remove dead code

2024-06-16T10:13:47Z

There are no calls of "watchdog_reset()" anymore anywhere in the tree since the WATCHDOG_RESET macro got removed in 942d07df0e79 ("watchdog: Remove WATCHDOG_RESET macro"). The only places the identifiers watchdog_disable and watchdog_init are called are in arch/arm/mach-omap2/, so those can obviously not refer to these instances. Hence these functions are not actually used at all and can be removed. As a bonus, this also removes two leftover references to WATCHDOG_RESET. Cc: Huan Wang Cc: Angelo Dureghello Signed-off-by: Rasmus Villemoes Reviewed-by: Stefan Roese

m68k: Remove common.h usage

2023-10-24T20:34:45Z

We can remove common.h from most cases of the code here, and only a few places need an additional header instead. Signed-off-by: Tom Rini Acked-by: Angelo Dureghello

arch: m68k: Implement relocation

2023-09-06T11:28:58Z

Implement relocation for M68K. Perform all the updates in start.S relocate_code in assemby, since it is a simple matter of traversing the dynsym table and adding relocation offset - MONITOR_BASE to all the items in that table. The necessity to deal with MONITOR_BASE is a specific of M68K, where the ELF entry point is at offset 0x400, which is the MONITOR_BASE, while TEXT_BASE is at offset 0 . This also removes the one last user of NEEDS_MANUAL_RELOC, so that could be finally cleaned up . Reviewed-by: Simon Glass Signed-off-by: Marek Vasut

m68k: move watchdog functions in mcf_wdt driver

2023-07-25T21:21:42Z

Move watchdog functions inside a separate watchdog driver. Signed-off-by: Angelo Dureghello --- Changes for v2: - none Changes for v3: - none

arch: m68k: Add QEMU specific RAMBAR workaround

2023-04-15T19:36:07Z

The QEMU emulation of m68k does not support RAMBAR accesses, add Kconfig option which inhibits those accesses, so that U-Boot can be started in m68k QEMU for CI testing purpopses until QEMU emulation improves. Signed-off-by: Marek Vasut

arch: m68k: Use existing CONFIG_MCFTMR instead of CFG_MCFTMR

2023-04-15T19:36:07Z

There is an existing CONFIG_MCFTMR Kconfig symbol, use it and drop all other instances of CFG_MCFTMR. This duality is likely a result of bogus conversion to Kconfig. Fixes: 7ff7b46e6ce ("m68k: rename CONFIG_MCFTMR to CFG_MCFTMR") Signed-off-by: Marek Vasut

m68k: rename CONFIG_MCFTMR to CFG_MCFTMR

2023-03-15T00:41:57Z

This is not a Kconfig option so changing to _CFG. Signed-off-by: Angelo Durgehello

global: Finish CONFIG -> CFG migration

2023-01-20T17:27:24Z

At this point, the remaining places where we have a symbol that is defined as CONFIG_... are in fairly odd locations. While as much dead code has been removed as possible, some of these locations are simply less obvious at first. In other cases, this code is used, but was defined in such a way as to have been missed by earlier checks. Perform a rename of all such remaining symbols to be CFG_... rather than CONFIG_... Signed-off-by: Tom Rini Reviewed-by: Simon Glass

m68k: Rename CONFIG_WATCHDOG_TIMEOUT to CONFIG_WATCHDOG_TIMEOUT_MSECS

2022-12-05T23:16:43Z

In practice, it is clear that the usage in m68k of CONFIG_WATCHDOG_TIMEOUT is setting a value in milliseconds. Rename this to the existing symbol and move to Kconfig. Signed-off-by: Tom Rini

global: Move remaining CONFIG_SYS_* to CFG_SYS_*

2022-12-05T21:06:08Z

The rest of the unmigrated CONFIG symbols in the CONFIG_SYS namespace do not easily transition to Kconfig. In many cases they likely should come from the device tree instead. Move these out of CONFIG namespace and in to CFG namespace. Signed-off-by: Tom Rini Reviewed-by: Simon Glass