linux-kernel - [PATCH 0/4] watchdog: add TI K3 SoC watchdog support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200228142331.13716-1-t-kristo@ti.com>
Date:   Fri, 28 Feb 2020 16:23:27 +0200
From:   Tero Kristo <t-kristo@...com>
To:     <wim@...ux-watchdog.org>, <linux@...ck-us.net>,
        <linux-watchdog@...r.kernel.org>
CC:     <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/4] watchdog: add TI K3 SoC watchdog support

Hi,

This series adds support for TI K3 SoC watchdog. This watchdog operates
in windowed mode, meaning if it is petted either too early or too late
compared to its time window, it will generate an error.

Patch #2 fixes a limitation in the watchdog core this causes, as
typically the keepalive timers pet watchdogs immediately when they are
started, and with the RTI watchdog, this causes an immediate reset (too
early petting of the watchdog timer.) Alternative approach to avoid this
would be to add timer within the K3 driver itself to ignore too early
petting when the watchdog is started. Feedback welcome how people want
to see this handled.

Patch #4 should be merged via the ARM SoC tree once driver side patches
are acceptable (I can handle this portion later on.)

-Tero

--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki