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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A6363C433F5 for ; Tue, 18 Jan 2022 01:35:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=yn5PGPuPVGihKzMjZiWtCR1/F+vVcJNj1JMtZ1bgRJ8=; b=MmixKKw30j1cN6 LZtIT0d1M8NRmibZDQB2kfnS+49/HN1wNNWoxs+ODVImi++FCNikx0Vbkj8OxsHN5xBH/2YQwPbIL V76FzbP4hBk9eVizVcYurJmFWNNnOCe5ZFD/WNrGOMS3fhICM6Qc2xmvkFckgH8PSZv+vt+YYFGjN W2kHnL7nML7tmJJY+CbHR8eFfZwI9XF1A0AJkXX1xsxgh6RrHpwUyYfmuNRBb5CeAi14BtAJFvQAA APOFN6R6QPNT17BqtB1jw0KDitYHbV5Xj0n2FKKWdM0gC8jiciD0mEVKHItCcJYn6RfQs6nP++nDV RjauiDtE2Of4Zryiav1w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1n9dFV-00GlSe-Af; Tue, 18 Jan 2022 01:25:25 +0000 Received: from eu-shark2.inbox.eu ([195.216.236.82]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1n9dFR-00GlRl-B1 for linux-arm-kernel@lists.infradead.org; Tue, 18 Jan 2022 01:25:23 +0000 Received: from eu-shark2.inbox.eu (localhost [127.0.0.1]) by eu-shark2-out.inbox.eu (Postfix) with ESMTP id 4BE4B1E005F5; Tue, 18 Jan 2022 03:25:18 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mail.ee; s=20150108; t=1642469118; bh=Cbmo9zzdZXPewDMITMeQMfnHGjPMBioKlh1IQUhsBxQ=; h=Date:From:To:Subject:Message-ID:In-Reply-To:References: Content-Type:X-ESPOL:from:date; b=MlXWID5ySVJJLPQhj/Lei5OCIAAYySnUfHFyzB/PLJhndtigEpcg+IYiSOUGLA4vN E07e+IerxIeiTvOQTOS/fkvC6RPniMHY02Lo5n0e2AVK8jQ7g0tMe5xTEKbLY5EGIn GKzWswZdwgW+NzR9vBzh0MfqZcJTaICiH8Z8dS2s= Received: from localhost (localhost [127.0.0.1]) by eu-shark2-in.inbox.eu (Postfix) with ESMTP id 3E4991E005F4; Tue, 18 Jan 2022 03:25:18 +0200 (EET) Received: from eu-shark2.inbox.eu ([127.0.0.1]) by localhost (eu-shark2.inbox.eu [127.0.0.1]) (spamfilter, port 35) with ESMTP id sc4amGnhCHPH; Tue, 18 Jan 2022 03:25:18 +0200 (EET) Received: from mail.inbox.eu (eu-pop1 [127.0.0.1]) by eu-shark2-in.inbox.eu (Postfix) with ESMTP id E78C91E005E9; Tue, 18 Jan 2022 03:25:17 +0200 (EET) Date: Tue, 18 Jan 2022 04:25:12 +0300 From: Boris Lysov To: Mark Rutland Cc: Guenter Roeck , linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: Missing ARM TWD Watchdog driver? Message-ID: <20220118042512.360ee83a@pc> In-Reply-To: <20220117170225.GB94025@C02TD0UTHF1T.local> References: <20220117190112.2b2c2f53@pc> <60dceae6-5c7c-9f2d-9fcb-5e849f1d8ce5@roeck-us.net> <20220117170225.GB94025@C02TD0UTHF1T.local> MIME-Version: 1.0 X-Virus-Scanned: OK X-ESPOL: 6NpmlY9HHDysjlqlQGetewt38GpVJY3o+OCk0Rhfgnn7NzCFfUoRMmO6mHAFPnHC3iM= X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220117_172521_589473_D26F60C4 X-CRM114-Status: GOOD ( 19.81 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Mark and Guenter, On Mon, 17 Jan 2022 17:02:25 +0000, Mark Rutland wrote: > On Mon, Jan 17, 2022 at 08:34:57AM -0800, Guenter Roeck wrote: > > On 1/17/22 8:01 AM, Boris Lysov wrote: > > > Hello everyone, > > > > > > I stumbled upon the ARM TWD Watchdog driver which seems to be missing (or > > > I'm just blind). > > > > > > As per commit a33f5c380c4bd3fa5278d690421b72052456d9fe ("Merge tag > > > 'xfs-5.17-merge-3' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux"), > > > multiple device trees declare usage of arm-twd: > > > > > > (...) > > > > > > and it is documented in > > > Documentation/devicetree/bindings/watchdog/arm,twd-wdt.yaml > > > > > > However I could not find the driver itself. I tried running > > > case-insensitive grep and ripgrep to no avail. Does this driver actually > > > exist? Is it gone? > > > > > > > I may be missing it, but I do not see any evidence that it ever existed. > > Likewise, AFAICT we added the binding but never the driver. > > Looking at the git history, that schema was introduced in commit: > > 50e02e9a030a9ae3 ("dt-bindings: timer: arm,twd: Convert to json-schema") > > ... and replaced Documentation/devicetree/bindings/timer/arm,twd.txt > > Per: > > $ git log --follow Documentation/devicetree/bindings/timer/arm,twd.txt > > That was introduced alongside a driver in commit: > > d8e0364364d333fe ("ARM: smp_twd: add device tree support") > > ... which only introduced a driver for the timer, and not the watchdog, > as the commit message notes. > > Thanks. > Mark. Now I understand there's no ARM TWD Watchdog driver. TYVM for your replies! _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel