[lkml]   [2020]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/7] watchdog: dw_wdt: Take Baikal-T1 DW WDT peculiarities into account
On Fri, Mar 06, 2020 at 04:27:40PM +0300, wrote:
> From: Serge Semin <>
> There were a few features enabled at the time of the Baikal-T1 SoC DW WDT
> IP synthesis, which weren't taken into account in the DW WDT driver available
> in the kernel. First of all the SoC engineers synthesized the watchdog core
> with WDT_USE_FIX_TOP set to false (don't really know why, but they did).
> Due to this the timer reset values weren't fixed as the driver expected
> but were initialized with a pre-defined values selected by the engineers.
> Secondly the driver expected that the watchdog APB bus and the timer had
> synchronous reference clocks, while Baikal-T1 SoC DW WDT was created with
> asynchronous ones. So the driver should enable two clock devices: APB bus
> clocks and a separate timer reference clock. Finally DW Watchdog Timer is
> capable of generating a pre-timeout interrupt if corresponding config is
> enabled. The problem was that the pre-timeout IRQ happens when the set
> timeout elapses, while the actual WDT expiration and subsequent reboot take
> place in the next timeout. This makes the pre-timeout functionality
> implementation a bit tricky, since in this case we would have to find a
> WDT timeout twice smaller the requested timeout. All of the changes described
> above are provided by the patches in this patchset.
> In addition traditionally we replaced the legacy plain text-based dt-binding
> file with yaml-based one, made some cleanups in the watchdog core code (just
> replaced time-unit numerical literals with corresponding macro) and added
> DebugFS nodes to ease the driver debug procedure.
> This patchset is rebased and tested on the mainline Linux kernel 5.6-rc4:
> commit 98d54f81e36b ("Linux 5.6-rc4").
> Signed-off-by: Serge Semin <>
> Signed-off-by: Alexey Malahov <>
> Cc: Maxim Kaurkin <>
> Cc: Pavel Parkhomenko <>
> Cc: Ramil Zaripov <>
> Cc: Ekaterina Skachko <>
> Cc: Vadim Vlasov <>
> Cc: Thomas Bogendoerfer <>
> Cc: Paul Burton <>
> Cc: Ralf Baechle <>
> Cc: Wim Van Sebroeck <>
> Cc: Guenter Roeck <>
> Cc: Philipp Zabel <>
> Cc: Rob Herring <>
> Cc: Mark Rutland <>
> Cc:
> Cc:
> Cc:
> Serge Semin (7):
> dt-bindings: watchdog: dw-wdt: Replace legacy bindings file with
> YAML-based one
> dt-bindings: watchdog: dw-wdt: Add watchdog TOPs array property
> watchdog: watchdog_dev: Use generic msec-per-sec macro
> watchdog: dw_wdt: Support devices with non-fixed TOP values
> watchdog: dw_wdt: Support devices with asynch clocks
> watchdog: dw_wdt: Add pre-timeouts support
> watchdog: dw_wdt: Add DebugFS files
> .../devicetree/bindings/watchdog/dw_wdt.txt | 24 -
> .../bindings/watchdog/snps,dw-wdt.yaml | 96 ++++
> drivers/watchdog/dw_wdt.c | 460 ++++++++++++++++--
> drivers/watchdog/watchdog_dev.c | 4 +-
> 4 files changed, 523 insertions(+), 61 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/watchdog/dw_wdt.txt
> create mode 100644 Documentation/devicetree/bindings/watchdog/snps,dw-wdt.yaml
> --
> 2.25.1


It appears our corporate email server changes the Message-Id field of
messages passing through it. Due to that the emails threading gets to be
broken. I'll resubmit the properly structured v2 patchset as soon as our
system administrator fixes the problem and all the questions, already raised by
the maintainers/reviewer, are settled. Sorry for the inconvenience caused me.


 \ /
  Last update: 2020-03-10 01:34    [W:0.059 / U:26.420 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site