diff options
| author | Rasmus Villemoes <rasmus.villemoes@prevas.dk> | 2024-05-28 13:13:20 +0200 |
|---|---|---|
| committer | Stefan Roese <sr@denx.de> | 2024-06-16 12:13:54 +0200 |
| commit | 4388ada7690e977f34cdab78b0df5c185a9e3c67 (patch) | |
| tree | 185e93a98324da429ab883c2cf970cf8f3ea1db3 /drivers/watchdog | |
| parent | 7a779a8d09234d1be1a85b3a49287d0512f24419 (diff) | |
| download | u-boot-4388ada7690e977f34cdab78b0df5c185a9e3c67.tar.gz u-boot-4388ada7690e977f34cdab78b0df5c185a9e3c67.tar.bz2 u-boot-4388ada7690e977f34cdab78b0df5c185a9e3c67.zip | |
wdt-uclass: watchdog_reset cleanup
watchdog_reset() is no longer called from anywhere, so we do not need
to define a dummy no-op function. Remove that definition, and update
references to say schedule() instead.
Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Reviewed-by: Stefan Roese <sr@denx.de>
Diffstat (limited to 'drivers/watchdog')
| -rw-r--r-- | drivers/watchdog/wdt-uclass.c | 19 |
1 files changed, 2 insertions, 17 deletions
diff --git a/drivers/watchdog/wdt-uclass.c b/drivers/watchdog/wdt-uclass.c index e2e7f9ab84..10be334e9e 100644 --- a/drivers/watchdog/wdt-uclass.c +++ b/drivers/watchdog/wdt-uclass.c @@ -30,7 +30,7 @@ struct wdt_priv { u32 timeout; /* * Time, in milliseconds, between calling the device's ->reset() - * method from watchdog_reset(). + * method from schedule(). */ ulong reset_period; /* @@ -222,21 +222,6 @@ int wdt_expire_now(struct udevice *dev, ulong flags) return ret; } -#if defined(CONFIG_WATCHDOG) -/* - * Called by macro WATCHDOG_RESET. This function be called *very* early, - * so we need to make sure, that the watchdog driver is ready before using - * it in this function. - */ -void watchdog_reset(void) -{ - /* - * Empty function for now. The actual WDT handling is now done in - * the cyclic function instead. - */ -} -#endif - static int wdt_pre_probe(struct udevice *dev) { u32 timeout = WATCHDOG_TIMEOUT_SECS; @@ -264,7 +249,7 @@ static int wdt_pre_probe(struct udevice *dev) priv->autostart = autostart; /* * Pretend this device was last reset "long" ago so the first - * watchdog_reset will actually call its ->reset method. + * schedule() will actually call its ->reset method. */ priv->next_reset = get_timer(0); |