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=-8.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=unavailable 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 A68DECA9EA0 for ; Fri, 25 Oct 2019 20:30:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 7A33421D7B for ; Fri, 25 Oct 2019 20:30:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1572035438; bh=Bb1ujteTR8xP3fNUIo5zPOH0/+KxNzcMSgBRw/Yby9g=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=wlCGgJna1NQk9ywV6rhpH0A6OhTb/SKtKurxDvT0gB+oMbUIJ7uT4Bm3VB441c3Y+ Fz7Y+8XFwyGQET5e+b72xP8W+ZWFzomavaSLp0vJqRaezyEMWjoM6uq0E6WyzVf2l/ YSSpceawdTyGg+QJ1txa4IjktbY6rs8UMkrPt0yU= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728370AbfJYUae (ORCPT ); Fri, 25 Oct 2019 16:30:34 -0400 Received: from mail-oi1-f196.google.com ([209.85.167.196]:33376 "EHLO mail-oi1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728273AbfJYUae (ORCPT ); Fri, 25 Oct 2019 16:30:34 -0400 Received: by mail-oi1-f196.google.com with SMTP id a15so2478219oic.0; Fri, 25 Oct 2019 13:30:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=DjnUodnaL6w0elyh2CsGwsstDrRTdxNuqmD9G+YqUd4=; b=cEdmt9X0RedGeE58QLRAjUCtEpWlXbZoqwElE2jizOvUrKkArrwEDToYVzdXpzeqGd UaG2X+U0IGq1dj44GLHKcogyV80hGl59HTzT6U+yjk3jQ3qMAGuFNPf5KnpNmpyJYoaT RZABGN8ldGvQ3fINoyxhF3d/Qp2daeCKeYdD7U1Jf1l0aegpObAuGg9AfyWThowB/NEh N1IdGwWZ4+kkLh9r76wqXnXeI5RroruqvM7BiH1jGKX3exKeX1FDpRsq/Gs3kXMWwO45 e6SvSTQ5IXZPxjCm52llzZjGh9MQtTTC9wmyWxZE67Kdu09CTlOJ2UKFnGL82I783oQ4 RpYg== X-Gm-Message-State: APjAAAV7BIFwowKm8CM8Ui03BwKk79+myEPLfg5YuP9vDYsa/3Ist7wI y+x/mlwpUjM2amliLXMM0Q== X-Google-Smtp-Source: APXvYqy/fDo5GIME57rCCB5sn8utMkgqqWQkRouqjcMDQCu4olP7uzs9etttYKNKUcq1tCCeLd1KXQ== X-Received: by 2002:aca:b256:: with SMTP id b83mr2268898oif.101.1572035431991; Fri, 25 Oct 2019 13:30:31 -0700 (PDT) Received: from localhost (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id l19sm842018oie.22.2019.10.25.13.30.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 25 Oct 2019 13:30:31 -0700 (PDT) Date: Fri, 25 Oct 2019 15:30:30 -0500 From: Rob Herring To: Xingyu Chen Cc: Wim Van Sebroeck , Guenter Roeck , Kevin Hilman , Neil Armstrong , Jerome Brunet , Qianggui Song , Jianxin Pan , Jian Hu , linux-watchdog@vger.kernel.org, linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH v3 2/4] dt-bindings: watchdog: add new binding for meson secure watchdog Message-ID: <20191025203030.GA28391@bogus> References: <1571983984-11771-1-git-send-email-xingyu.chen@amlogic.com> <1571983984-11771-3-git-send-email-xingyu.chen@amlogic.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1571983984-11771-3-git-send-email-xingyu.chen@amlogic.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Fri, Oct 25, 2019 at 02:13:02PM +0800, Xingyu Chen wrote: > The binding targets the Meson-A/C series compatible SoCs, in which the > watchdog registers are in secure world. > > Signed-off-by: Xingyu Chen > --- > .../bindings/watchdog/amlogic,meson-sec-wdt.yaml | 34 ++++++++++++++++++++++ > 1 file changed, 34 insertions(+) > create mode 100644 Documentation/devicetree/bindings/watchdog/amlogic,meson-sec-wdt.yaml > > diff --git a/Documentation/devicetree/bindings/watchdog/amlogic,meson-sec-wdt.yaml b/Documentation/devicetree/bindings/watchdog/amlogic,meson-sec-wdt.yaml > new file mode 100644 > index 00000000..0bbc807 > --- /dev/null > +++ b/Documentation/devicetree/bindings/watchdog/amlogic,meson-sec-wdt.yaml > @@ -0,0 +1,34 @@ > +# SPDX-License-Identifier: (GPL-2.0+ OR MIT) > +# Copyright (c) 2019 Amlogic, Inc > +%YAML 1.2 > +--- > +$id: "http://devicetree.org/schemas/power/amlogic,meson-sec-wdt.yaml#" > +$schema: "http://devicetree.org/meta-schemas/core.yaml#" > + > +title: Amlogic Meson Secure Watchdog Timer > + > +maintainers: > + - Xingyu Chen > + > +description: |+ > + Secure Watchdog Timer used in Meson-A/C series Compatible SoCs > + > +properties: > + compatible: > + enum: > + - amlogic,meson-sec-wdt If there are no other properties, then you don't need this. Just have the secure firmware driver instantiate the watchdog. > + > + secure-monitor: > + description: phandle to the secure-monitor node > + $ref: /schemas/types.yaml#/definitions/phandle > + > +required: > + - compatible > + - secure-monitor > + > +examples: > + - | > + watchdog { > + compatible = "amlogic,meson-sec-wdt"; > + secure-monitor = <&sm>; > + }; > -- > 2.7.4 >