Received: by 2002:a25:1506:0:0:0:0:0 with SMTP id 6csp677132ybv; Thu, 20 Feb 2020 05:28:24 -0800 (PST) X-Google-Smtp-Source: APXvYqz63zCaPsKctKs9A12Q6QD1mdxmwssx6E3rzepep7V9MwYHIe4pZ1wbjVAsxXOdPoOF7g9O X-Received: by 2002:aca:b504:: with SMTP id e4mr2050051oif.28.1582205303879; Thu, 20 Feb 2020 05:28:23 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1582205303; cv=none; d=google.com; s=arc-20160816; b=PKtkmcUTxwxItEmGYr4aHfNPabPUNhGl7p1joFXuPzH96t9xAYtDPHgl7CfMbb/v25 +3NJG2Jgt601AqAzGk4LatehDm4joEARJzlFp5dhy5/VaxNOHuagcaP8dq2av6rkENrT 9I9fsX8Hlm7FDnG2GPjh/Oo0XW6V3JYMyUB48xaCXbExREH2q21GZ2reFrFYO0mtIu4z p65LgeBmR6k1d8WXAy8vPkwKcDeSXJs55S9+2YZSRM6U2n88O9liopg6rIlmeiEYUyAe 21ErGm68R0C3IsvQieEejcscD/CGQ8jSqB/GzZ5ehyGphGennY2vusXsoBx5y7Vt44hI Ub1Q== 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=LQqIT5T64VKhhQT6eFbemZXOlBbxB+vvUJxhALSyT34=; b=wWzWAz+MYWpMoJ+85a+UoFvk/mSNwqucU3AqL0bdB5vg0Rv/7wKnlO1sKwjmQQ0E9J KpteZXSHyZe87pXGhd7B5AaSGqwVPZ6seiio0BlNGriOZ3fbiRQYDJV7nD2Yos+6u8br DNdJuijS133WKswIxnRKBVi1BTkpfLyH2j5zgfHa5KWjNcU8S3z+ip7IdJ1TYK0Ly94u 7lvN20SuvFQdipJ8SVW1GBpTnKdGsKYepL1spuRDRwF0RX/czY/zw45kbQiXLIbRff4A zoUV/SpKb+LlHchyk32QgV9rKUbRpUUGlykDYoVw8ZxbNoR1ZqCT71FybXJo9UpFdBpH 9wXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=ETWCB9au; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w5si1569021otk.244.2020.02.20.05.28.11; Thu, 20 Feb 2020 05:28:23 -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=@kernel.org header.s=default header.b=ETWCB9au; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728245AbgBTN15 (ORCPT + 99 others); Thu, 20 Feb 2020 08:27:57 -0500 Received: from mail.kernel.org ([198.145.29.99]:56366 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726959AbgBTN14 (ORCPT ); Thu, 20 Feb 2020 08:27:56 -0500 Received: from mail-qk1-f175.google.com (mail-qk1-f175.google.com [209.85.222.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id CD720222C4; Thu, 20 Feb 2020 13:27:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1582205275; bh=LRERjOY5swhgYq3TNDFqarey7d7DB+nwUJMGhi6oW7I=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=ETWCB9au7GNELIvo2IGphOuMC7YLOuI9PCos8dfJeskBQpqRE9gfhSM/3dYm1hNfQ 2+spmMhLjQy3O803GwZkQTSPkJ/g6oQqkLq/GAlXUOKsIRrlaqsih03lVpecyg5ceO j/kEiaLM42UzlHx+s3/fjdb6NH2uMpau8TVCPWH8= Received: by mail-qk1-f175.google.com with SMTP id a141so3490257qkg.6; Thu, 20 Feb 2020 05:27:55 -0800 (PST) X-Gm-Message-State: APjAAAU5VN/68yT5A8b4H5dbRWFBnXY/ikAo3Cd0y05KAxgUxwkzjSGF VImFrswwT63uTmoCc5MGXDmeSIVwTMTqqd3fMg== X-Received: by 2002:a37:6457:: with SMTP id y84mr28648400qkb.254.1582205274941; Thu, 20 Feb 2020 05:27:54 -0800 (PST) MIME-Version: 1.0 References: <1579087831-94965-1-git-send-email-jianxin.pan@amlogic.com> <1579087831-94965-3-git-send-email-jianxin.pan@amlogic.com> In-Reply-To: <1579087831-94965-3-git-send-email-jianxin.pan@amlogic.com> From: Rob Herring Date: Thu, 20 Feb 2020 07:27:43 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v6 2/4] dt-bindings: power: add Amlogic secure power domains bindings To: Jianxin Pan Cc: Kevin Hilman , "open list:ARM/Amlogic Meson..." , Neil Armstrong , Jerome Brunet , Martin Blumenstingl , "open list:THERMAL" , "linux-kernel@vger.kernel.org" , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , 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 On Wed, Jan 15, 2020 at 5:30 AM 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 > --- > .../bindings/power/amlogic,meson-sec-pwrc.yaml | 40 ++++++++++++++++++++++ > include/dt-bindings/power/meson-a1-power.h | 32 +++++++++++++++++ > 2 files changed, 72 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..af32209 > --- /dev/null > +++ b/Documentation/devicetree/bindings/power/amlogic,meson-sec-pwrc.yaml > @@ -0,0 +1,40 @@ > +# 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: |+ > + Secure Power Domains used in Meson A1/C1 SoCs, and should be the child node > + of secure-monitor. > + > +properties: > + compatible: > + enum: > + - amlogic,meson-a1-pwrc > + > + "#power-domain-cells": > + const: 1 > + > +required: > + - compatible > + - "#power-domain-cells" > + > +examples: > + - | > + secure-monitor { > + compatible = "amlogic,meson-gxbb-sm"; > + > + pwrc: power-controller { > + compatible = "amlogic,meson-a1-pwrc"; > + #power-domain-cells = <1>; > + }; > + } Missing ';': Error: Documentation/devicetree/bindings/power/amlogic,meson-sec-pwrc.example.dts:27.5-6 syntax error FATAL ERROR: Unable to parse input tree Please fix this as linux-next is now failing dt_binding_check. Rob