Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp2202325ybv; Fri, 14 Feb 2020 13:34:06 -0800 (PST) X-Google-Smtp-Source: APXvYqxgk4m3JOo18e/cIFhQ8g6Zn3i1pDcC9n8m23vlNiAgmgswKpZy/tcQaK/8kLzPOJyR7ngz X-Received: by 2002:aca:5248:: with SMTP id g69mr3156063oib.106.1581716046436; Fri, 14 Feb 2020 13:34:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1581716046; cv=none; d=google.com; s=arc-20160816; b=CtVWV5uFABv8dSHwwl4CXOL3WOxACOexVcQInICE+n/Vz3za44PhK6iy6bNAL663Ag oc5L/aTk717Sjou9f+vOb6VGitzchoIxeAlbRBMQMY0+0rvgUCHYBaC1dZ9RowiN1yR/ 4HG14Skv1ecxXsT/PZT0Is9vkV1cyKbsI7AghQw26iJRc0Pl8U8Jws3iKSNx9IkkJObJ hwAl3Mkfl7RKmL7l7oXTxgvmrBvfDddwOx6zDPk9bnuMXhidBPJivFiLB+tpe2obJJaU rSUk7hcL4oaDg2874MVshjFkKQJDDKFoJ+csd1Z9ysS7QckZbeCmOtk43bVvX7kzi/4O fksQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=BZKc7Iw5Ao6DeSW088cynAow9LgysvsQp4C3aBIY+yc=; b=aAojMBKO3Rsve8dI1mNjmQZhCkRjzS22EviBU4slWgLpHcqr6q5Opr2nccyk+jXuJS 4RbPl5O6UM+/92IMOMp8OjkJR6H5WqacskJFZlU4ocka1Zc1XGshStPL8sfSQk/oARGW zL8myiRXpqPgrIma8PipA5WiRPuxC3awlNLFBTbWXm39XZUSF+7wRbpbXYmqMZWUIVFH yth8OilOdgHbhWdTX/p1jtoJ+K+CrtPmsudXub142j1ycXNFIjDk1mGnbQG7Cgo3YrHd JW6uqHHgcaRUWY34qlJR4MigUZc98XZMJGobn8CsxndJKK/PUJzotYU6GUMbHQyd/Nzv +cwA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b="WMQs/0hL"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f81si3348751oig.110.2020.02.14.13.33.54; Fri, 14 Feb 2020 13:34:06 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b="WMQs/0hL"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388965AbgBNVcX (ORCPT + 99 others); Fri, 14 Feb 2020 16:32:23 -0500 Received: from mail-io1-f67.google.com ([209.85.166.67]:35879 "EHLO mail-io1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388065AbgBNVcX (ORCPT ); Fri, 14 Feb 2020 16:32:23 -0500 Received: by mail-io1-f67.google.com with SMTP id d15so12128288iog.3 for ; Fri, 14 Feb 2020 13:32:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BZKc7Iw5Ao6DeSW088cynAow9LgysvsQp4C3aBIY+yc=; b=WMQs/0hLj9/SxQ3vyxLv+3rncv4W8okLOKv6C0paboIrojTdECQfyJCrhOCRT0fx4G oM3HAXuULlD2gvgTYP2NxZj61hNw6RN40PPsvbd226CVbYcK1BLyT/VvhFm1NUfXzdYg VY8r0gqWL+Gg+F2FX6wfqU9i/m0gWGApmJFk8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BZKc7Iw5Ao6DeSW088cynAow9LgysvsQp4C3aBIY+yc=; b=mqqodJIXZYP+tIYN++LTtlYAf9JnjEYCQncZepN58m6r/WTBuxZCrkBPxlOJboEgJi 3ngPK6gm79jMpmvm5cUlJIMOzvt89p2Xh9VktbqKaAP2WKTQiSNjs8zroy5KiRemguqF aE6goPV1PbcUwvgVtpF7oo++W2gUvttPjX+cmOUxP9B0q1MowyLwsFOzu2w6flMslhiX SMu1KPiouuQD2We3D+L3D6g/tX1LbUQfIb/BIMUsxPb7Hx2zaJpUnS6ZCs5ROR1m3+f/ MAP7c+s2gCuNxKdbgRuwjn/N4jbSRj7OG5XEjX0foVFowiW7SIUdqSV/AMdKjr06L54f ssDw== X-Gm-Message-State: APjAAAUwbs679wZkXpv8UkhfYaRXphA5u0KiDHGzNvKBo6qXI2HR/wEd t6yXO9tlFEPL5Y1jsiBTYdifAEMLzWxZVbryEkQKoeIy X-Received: by 2002:a5d:8796:: with SMTP id f22mr3932931ion.163.1581715942261; Fri, 14 Feb 2020 13:32:22 -0800 (PST) MIME-Version: 1.0 References: <20200214062637.216209-1-evanbenn@chromium.org> <20200214172512.2.I7c8247c29891a538f258cb47828d58acf22c95a2@changeid> <804d3cc5-688d-7025-cb87-10b9616f4d9b@roeck-us.net> In-Reply-To: <804d3cc5-688d-7025-cb87-10b9616f4d9b@roeck-us.net> From: Julius Werner Date: Fri, 14 Feb 2020 13:32:09 -0800 Message-ID: Subject: Re: [PATCH 2/2] watchdog: Add new arm_smc_wdt watchdog driver To: Guenter Roeck Cc: Evan Benn , LKML , Julius Werner , Bjorn Andersson , Mauro Carvalho Chehab , Marcin Juszkiewicz , Catalin Marinas , Olof Johansson , Leonard Crestez , Jonathan Cameron , Dinh Nguyen , linux-arm-kernel@lists.infradead.org, Greg Kroah-Hartman , Will Deacon , linux-watchdog@vger.kernel.org, Rob Herring , Wim Van Sebroeck , =?UTF-8?B?Q2zDqW1lbnQgUMOpcm9u?= , Shawn Guo , "David S. Miller" , Anson Huang Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > with a Secure Monitor firmware to forward watchdog operations to > > firmware via a Secure Monitor Call. This may be useful for platforms > > using TrustZone that want the Secure Monitor firmware to have the final > > control over the watchdog. > > > > As written, one would assume this to work on all systems implementing > ARM secure firmware, which is not the case. Please select a different > name, and provide information about the systems where this is actually > supported. > > If it happens to be standardized, we will need a reference to the standard > supported. This needs to distinguish from IMX_SC_WDT, which also supports > a secure monitor based watchdog (but doesn't claim to be generic). Back when I wrote this I was hoping it could be something that other platforms can pick up if they want to, but that hasn't happened yet and the code on the Trusted Firmware side is still MediaTek-specific. Unfortunately Arm doesn't make it easy to write generic SMC interfaces and my attempts to change that haven't been very fruitful for now. So yes, probably makes sense to treat this as MediaTek-specific for now, we can still consider expanding it later if there's interest from other platforms. (I would like to avoid every vendor writing their own driver and SMC interface for this, although looking at that IMX driver it seems that we're already there.)