[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <422fc81c-81d7-4473-92b6-9d112e6e247a@kernel.org>
Date: Mon, 14 Jul 2025 08:04:47 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Sangwook Shin <sw617.shin@...sung.com>, alim.akhtar@...sung.com,
wim@...ux-watchdog.org, linux@...ck-us.net
Cc: linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org,
linux-watchdog@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 RESEND 3/5] watchdog: s3c2410_wdt: Increase max timeout
value of watchdog
On 14/07/2025 07:54, Sangwook Shin wrote:
> Increase max_timeout value from 55s to 3664647s (1017h 57min 27s) with
> 38400000 frequency system if the system has 32-bit WTCNT register.
>
> cat /sys/devices/platform/10060000.watchdog_cl0/watchdog/watchdog0/max_timeout
> 3664647
>
> [ 0.302473] s3c2410-wdt 10060000.watchdog_cl0: Heartbeat: count=1099394100000, timeout=3664647, freq=300000
> [ 0.302479] s3c2410-wdt 10060000.watchdog_cl0: Heartbeat: timeout=3664647, divisor=256, count=1099394100000 (fff8feac)
> [ 0.302510] s3c2410-wdt 10060000.watchdog_cl0: starting watchdog timer
> [ 0.302722] s3c2410-wdt 10060000.watchdog_cl0: watchdog active, reset enabled, irq disabled
>
> If system has 32-bit WTCNT, add QUIRK_HAS_32BIT_MAXCNT to its quirk flags, then
> it will operation with 32-bit counter. If not, with 16-bit counter like previous.
I claim that this patch fixes nothing, because there is no user of
QUIRK_HAS_32BIT_MAXCNT.
Best regards,
Krzysztof
Powered by blists - more mailing lists