Received: by 2002:a25:b323:0:0:0:0:0 with SMTP id l35csp728282ybj; Thu, 19 Sep 2019 22:26:16 -0700 (PDT) X-Google-Smtp-Source: APXvYqyUmYW1E1XjfPlWwrXY9CvpwZr3UMc0pevbZ8XbeyS1rVUhFU84l/Hj7PziQsnjdPx9PHmG X-Received: by 2002:a05:6402:1688:: with SMTP id a8mr10932497edv.225.1568957176821; Thu, 19 Sep 2019 22:26:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568957176; cv=none; d=google.com; s=arc-20160816; b=xs3GnYGeY2bSlwy6lPrSzTifQ61LgLWuYEjHAQWXLUUP58dJIZTJgwvLRcvs5oar0s W+zPziZQ4S9XFa/1ckp8HJ0vNCc+mt8dX5g6KrrdPCPdmN/dE2aE+jPJBmdSl6VU8gLA 7FMj7W8ubOm24L4F1lz25UCnv2YVm6I97Xs30ZcgUQiOjJTOhMlPTc7l5AtHOSMr/g2o EilNakfgl7gu1ls4in9D9sGVzcYOC2xEAYVg+HLa7DTJrMtOjx1YTwjJdhBFrdEy4BjO o4DMQu9kPewxNo/wkRy3lrHYLN/YCFOaXYwmEIOrqzBcnJaCLRfUpMcnmljlD65xAOss 96bQ== 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=6SLgslheBeIIJex/gf/ZVhEBmirzOWHGUduUXl+JfS0=; b=tKqEGhEKzDI4Q+VDD/XNOyHRvTQNygQDXnXHu3MxxHP1cPuQCXP97v1z3yi3g1QFHa WD/KzCUxF0OPHQJzppdAZXp/PIqUayje/9+gl698ikafvjenF9+cB+98zAbkpNAgaTmn o1wq+Tg8DHI3AM0C3cqziQSRqPdvR/AU2xCeSqPcmeNXf4qLWFYnCAVMs664ptOWHiqZ P9bCSEaX4srygr4H3Uny9+t0hX9nzpynERP2VeOt/4XOOXG6tFaky+hmdToEGcQISg4V fZYB9gkm1jSq2dZTVSto2YkYCibtqi12mjhujn2h6lI+svHlrAofRtkbLPSLUWCwcyuo 1M9Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@googlemail.com header.s=20161025 header.b=f8nGhVnv; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=googlemail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p14si560782ejn.192.2019.09.19.22.25.53; Thu, 19 Sep 2019 22:26:16 -0700 (PDT) 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=@googlemail.com header.s=20161025 header.b=f8nGhVnv; 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=QUARANTINE sp=QUARANTINE dis=NONE) header.from=googlemail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2392467AbfISUHL (ORCPT + 99 others); Thu, 19 Sep 2019 16:07:11 -0400 Received: from mail-oi1-f195.google.com ([209.85.167.195]:39170 "EHLO mail-oi1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2390722AbfISUHL (ORCPT ); Thu, 19 Sep 2019 16:07:11 -0400 Received: by mail-oi1-f195.google.com with SMTP id w144so3859155oia.6; Thu, 19 Sep 2019 13:07:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6SLgslheBeIIJex/gf/ZVhEBmirzOWHGUduUXl+JfS0=; b=f8nGhVnviG2KbGnxig/mqrpCztbeYB17qB2d4v8zgIMpIo21id++eyGrhRa7Hetlhu 1uIaChRD0JXsIkhaEnLlOVilPn+4x4RCBwn4qftOj/Hn1jiDkcWSr9iSRfpGqYg8IPyg p6KZ5T0M5XXE7g4URtoFpVBwAr8qDD1kwXGZhmKQ5TN4D/ZBt9h1HabeDijheKoZ1Hq6 Am7QREthxBCAoFRWZlZc9Dn8FvVmj/Ct4TgYQLr4ctdbmmcuJtv86n7ETES+bEZxL1mQ EVg7zzKRiWTN263W8ohXIHHzWdDRk8eIf0Lm/Lzn+chRgIy7X91h9B9AXapeP4UZEFK4 1Pqg== 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=6SLgslheBeIIJex/gf/ZVhEBmirzOWHGUduUXl+JfS0=; b=LRo5IFeo7bCrSGTPwzfrS3V9994tSJ6StNPbYplCww/oZi062QD+1Ceusj+wGxsKTc 2S1ZWmHUWjuU7/+GG38QkQ8zFQlUUun4bmwcy73ioa/dbMnMFM5sby0WaCGgbA8EhpfW pUPte2TuX/Z/tWC3hHILfw4liAmCvP4JV75rm/kCPYK4YCFPpVwG0M69vl9ogyUAE1Fh Hj8ODuEtG3JLKpAyzS2mvqr84BBF+UQRbUGq3769TT0vm4LXPokdKWg06XHLkAElbyj7 J+1oIHZG0l1QesIKgLM0CvON8ccbM/SQbWZ3uS66kyTD+sdc/XBzv5LhW9+K886WXoqk iYig== X-Gm-Message-State: APjAAAUzfXZ6uql9XutpVXopOzfL846dSj/7bH8GtlgN/4KY23ZbsorT 8MaLMGXdjmQzJ4AWbSABlQe2Yq0UrmSCuY5ZJPPiDOW5 X-Received: by 2002:aca:3ad6:: with SMTP id h205mr3915280oia.129.1568923630403; Thu, 19 Sep 2019 13:07:10 -0700 (PDT) MIME-Version: 1.0 References: <1568895064-4116-1-git-send-email-jianxin.pan@amlogic.com> <1568895064-4116-2-git-send-email-jianxin.pan@amlogic.com> In-Reply-To: <1568895064-4116-2-git-send-email-jianxin.pan@amlogic.com> From: Martin Blumenstingl Date: Thu, 19 Sep 2019 22:06:59 +0200 Message-ID: Subject: Re: [PATCH 1/3] dt-bindings: power: add Amlogic secure power domains bindings To: Jianxin Pan Cc: Kevin Hilman , linux-amlogic@lists.infradead.org, Zhiqiang Liang , Rob Herring , Neil Armstrong , Jerome Brunet , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, Jian Hu , Hanjie Lin , Victor Wan , Xingyu Chen 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 Hi Jianxin, On Thu, Sep 19, 2019 at 2:11 PM Jianxin Pan wrote: > > Add the bindings for the Amlogic Secure power domains, controlling the > secure power domains. > > The bindings targets the Amlogic A1 and C1 compatible SoCs, in which the > power domain registers are in secure world. > > Signed-off-by: Jianxin Pan > Signed-off-by: Zhiqiang Liang > --- > .../bindings/power/amlogic,meson-sec-pwrc.yaml | 32 ++++++++++++++++++++++ > include/dt-bindings/power/meson-a1-power.h | 32 ++++++++++++++++++++++ > 2 files changed, 64 insertions(+) > create mode 100644 Documentation/devicetree/bindings/power/amlogic,meson-sec-pwrc.yaml > create mode 100644 include/dt-bindings/power/meson-a1-power.h > > diff --git a/Documentation/devicetree/bindings/power/amlogic,meson-sec-pwrc.yaml b/Documentation/devicetree/bindings/power/amlogic,meson-sec-pwrc.yaml > new file mode 100644 > index 00000000..327e0d9 > --- /dev/null > +++ b/Documentation/devicetree/bindings/power/amlogic,meson-sec-pwrc.yaml > @@ -0,0 +1,32 @@ > +# SPDX-License-Identifier: (GPL-2.0+ OR MIT) > +# Copyright (c) 2019 Amlogic, Inc > +# Author: Jianxin Pan > +%YAML 1.2 > +--- > +$id: "http://devicetree.org/schemas/power/amlogic,meson-sec-pwrc.yaml#" > +$schema: "http://devicetree.org/meta-schemas/core.yaml#" > + > +title: Amlogic Meson Secure Power Domains > + > +maintainers: > + - Jianxin Pan > + > +description: |+ > + A1/C1 series The Secure Power Domains node should be the child of a syscon > + node with the required property. > + > +properties: > + compatible: > + enum: > + - amlogic,meson-a1-pwrc > + > +required: > + - compatible > + > +examples: > + - | > + pwrc: power-controller { > + compatible = "amlogic,meson-a1-pwrc"; > + }; not a comment about this binding but about the secure monitor in general: there's a recent discussion about the secure monitor in the nvmem bindings: [0] Martin [0] https://www.spinics.net/lists/arm-kernel/msg750010.html