Historically, the reset_cpu() function had an `addr` parameter which was
meant to pass in an address of the reset vector location, where the CPU
should reset to. This feature is no longer used anywhere in U-Boot as
all reset_cpu() implementations now ignore the passed value. Generic
code has been added which always calls reset_cpu() with `0` which means
this feature can no longer be used easily anyway.
Over time, many implementations seem to have "misunderstood" the
existence of this parameter as a way to customize/parameterize the reset
(e.g. COLD vs WARM resets). As this is not properly supported, the
code will almost always not do what it is intended to (because all
call-sites just call reset_cpu() with 0).
To avoid confusion and to clean up the codebase from unused left-overs
of the past, remove the `addr` parameter entirely. Code which intends
to support different kinds of resets should be rewritten as a sysreset
driver instead.
This transformation was done with the following coccinelle patch:
@@
expression argvalue;
@@
- reset_cpu(argvalue)
+ reset_cpu()
@@
identifier argname;
type argtype;
@@
- reset_cpu(argtype argname)
+ reset_cpu(void)
{ ... }
Signed-off-by: Harald Seiler <hws@denx.de>
Reviewed-by: Simon Glass <sjg@chromium.org>
|
||
|---|---|---|
| .. | ||
| bcm11130 | ||
| bcm11130_nand | ||
| bcm23550_w1d | ||
| bcm28155_ap | ||
| bcm28155_w1d | ||
| bcm911360_entphn | ||
| bcm911360_entphn-ns | ||
| bcm911360k | ||
| bcm958300k | ||
| bcm958300k-ns | ||
| bcm958305k | ||
| bcm958622hr | ||
| bcm958712k | ||
| bcm963158 | ||
| bcm968360bg | ||
| bcm968380gerg | ||
| bcm968580xref | ||
| bcm_ep | ||
| bcmcygnus | ||
| bcmns2 | ||
| bcmns3 | ||
| bcmnsp | ||
| bcmstb | ||