[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1jsfl4wv4a.fsf@starbuckisacylon.baylibre.com>
Date: Tue, 06 Sep 2022 14:21:26 +0200
From: Jerome Brunet <jbrunet@...libre.com>
To: Philippe Boos <pboos@...libre.com>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
Guenter Roeck <linux@...ck-us.net>,
Neil Armstrong <narmstrong@...libre.com>
Cc: Kevin Hilman <khilman@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
"open list:WATCHDOG DEVICE DRIVERS" <linux-watchdog@...r.kernel.org>,
"moderated list:ARM/Amlogic Meson SoC support"
<linux-arm-kernel@...ts.infradead.org>,
"open list:ARM/Amlogic Meson SoC support"
<linux-amlogic@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] watchdog: meson: keep running if already active
On Mon 01 Aug 2022 at 11:21, Philippe Boos <pboos@...libre.com> wrote:
> If the watchdog is already running (e.g.: started by bootloader) then
> the kernel driver should keep the watchdog active but the amlogic driver
> turns it off.
>
> Let the driver fix the clock rate if already active because we do not
> know the previous timebase value. To avoid unintentional resetting we
> temporarily set it to its maximum value.
>
> Then keep the enable bit if is was previously active.
>
> Signed-off-by: Philippe Boos <pboos@...libre.com>
Reviewed-by: Jerome Brunet <jbrunet@...libre.com>
Powered by blists - more mailing lists