From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CAF1CC3F2D2 for ; Fri, 28 Feb 2020 14:24:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9F598246AC for ; Fri, 28 Feb 2020 14:24:04 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=ti.com header.i=@ti.com header.b="y3Iuy0NE" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726694AbgB1OYE (ORCPT ); Fri, 28 Feb 2020 09:24:04 -0500 Received: from lelv0143.ext.ti.com ([198.47.23.248]:55408 "EHLO lelv0143.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726388AbgB1OYE (ORCPT ); Fri, 28 Feb 2020 09:24:04 -0500 Received: from fllv0034.itg.ti.com ([10.64.40.246]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 01SENh5g077109; Fri, 28 Feb 2020 08:23:43 -0600 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1582899823; bh=EEILE+Fex4n/42JxlV2SbtmSLAQuNLKLGkMArgUzilk=; h=From:To:CC:Subject:Date; b=y3Iuy0NERZnwgCiULydlgmNtajn4TulIpbhihnoTF6em92j2Lqor/NrixcTv0YAV9 r11bXEOSTgn45gKt3krlKG/i7MrTSj2IURazAOkF8DzQ/rj2RpTi8OTwQogdwZvKub 07Y8KfqK4DIkx1LhYzEKnAhFN3rYrd/sEtstW7X8= Received: from DFLE110.ent.ti.com (dfle110.ent.ti.com [10.64.6.31]) by fllv0034.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 01SENh9F016625 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Fri, 28 Feb 2020 08:23:43 -0600 Received: from DFLE105.ent.ti.com (10.64.6.26) by DFLE110.ent.ti.com (10.64.6.31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1847.3; Fri, 28 Feb 2020 08:23:43 -0600 Received: from lelv0326.itg.ti.com (10.180.67.84) by DFLE105.ent.ti.com (10.64.6.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1847.3 via Frontend Transport; Fri, 28 Feb 2020 08:23:43 -0600 Received: from sokoban.bb.dnainternet.fi (ileax41-snat.itg.ti.com [10.172.224.153]) by lelv0326.itg.ti.com (8.15.2/8.15.2) with ESMTP id 01SENf3w049600; Fri, 28 Feb 2020 08:23:41 -0600 From: Tero Kristo To: , , CC: Subject: [PATCH 0/4] watchdog: add TI K3 SoC watchdog support Date: Fri, 28 Feb 2020 16:23:27 +0200 Message-ID: <20200228142331.13716-1-t-kristo@ti.com> X-Mailer: git-send-email 2.17.1 MIME-Version: 1.0 Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-watchdog-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-watchdog@vger.kernel.org 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