Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3971040ybl; Mon, 26 Aug 2019 03:30:37 -0700 (PDT) X-Google-Smtp-Source: APXvYqxOgQ7CxruJLD+0MV/DYdNRHIQ7J/mpTHl/KTMlS31tcbpoWFa4WT2uFrOgy1oVtsKstDAi X-Received: by 2002:a63:394:: with SMTP id 142mr15787886pgd.43.1566815437126; Mon, 26 Aug 2019 03:30:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566815437; cv=none; d=google.com; s=arc-20160816; b=YwEkCa0+N/A4y+jzTlNfSIUb5MzypZZiMg9Ut93EG8koBOw/Fz4Wge0Y6lDzcqd62C E5rpPUrp7uf6LHxhUAavK91n3Ek0pJzi+H9Q6wFSUQJ6sH+iGn12ehTao3wqduOWfgBR O+WZO1fMrHDZlkRPlm+CcFOmJocwAqUbbmlWByKK5XozA5w0AG4X2WTyqwc41+iq01rU eWuZI/e88zPhB8VsZsjizcNx/T5Qpop60hfxICJHUce7laqUN87xlSOOrXpQngrlzPLY dpeFUGGGNw81mSHDFM2G++5T1SDH9Q67l0UNDOG1ZOao03EjAjEDnpcUUUaB0RPFcckC 2D5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=1fnIVbqtikPiF5Mj4OQFRUnOfHV2Bip3dSGQ2gj08z8=; b=opvF08esqjDE8It1Gs2q8kRIkueQsFkrhcPEVo618Kv37ycEZlNuuRmxsA2Nhsf6YR yjWKADhlqOaIWDwuZrdwirOgtiietsdiDql2VY8Gp3Z/amfc05hgWpA9n2zxING3iBLi RNuk/KQ94/3tcMzfwv2vp+OjOBo8a2QwLPXf/wAbikWkVFkx1H5Za3t2pCG2AEGT22BJ NeY8qne6kogDb/cEQgCJAJogPPR88uqiZMxi144au3CHAXZZjvInkJCl4ASHBPCVpNCW jFaqTGF7+k/TzZRgnvREhuBCKwu67+AAmI9zpB6CtfhO6pM/1ObhP7OwWx/U4LqwMdtL JHgg== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u3si8953983plz.201.2019.08.26.03.30.21; Mon, 26 Aug 2019 03:30:37 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731124AbfHZJw7 (ORCPT + 99 others); Mon, 26 Aug 2019 05:52:59 -0400 Received: from mga02.intel.com ([134.134.136.20]:18290 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726616AbfHZJw6 (ORCPT ); Mon, 26 Aug 2019 05:52:58 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Aug 2019 02:52:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,431,1559545200"; d="scan'208";a="181327932" Received: from linux.intel.com ([10.54.29.200]) by fmsmga007.fm.intel.com with ESMTP; 26 Aug 2019 02:52:57 -0700 Received: from [10.226.39.22] (ekotax-mobl.gar.corp.intel.com [10.226.39.22]) by linux.intel.com (Postfix) with ESMTP id B73805807C5; Mon, 26 Aug 2019 02:52:55 -0700 (PDT) Subject: Re: [PATCH v2 1/2] dt-bindings: reset: Add YAML schemas for the Intel Reset controller To: Rob Herring Cc: Philipp Zabel , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , cheol.yong.kim@intel.com, chuanhua.lei@linux.intel.com, qi-ming.wu@intel.com References: <42039170811f798b8edc66bf85166aefe7dbc903.1566531960.git.eswara.kota@linux.intel.com> From: Dilip Kota Message-ID: <746ed130-a1ae-0cc2-5060-70de95cdf2fe@linux.intel.com> Date: Mon, 26 Aug 2019 17:52:52 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rob, On 8/23/2019 8:25 PM, Rob Herring wrote: > On Fri, Aug 23, 2019 at 12:28 AM Dilip Kota wrote: >> Add YAML schemas for the reset controller on Intel >> Lightening Mountain (LGM) SoC. >> >> Signed-off-by: Dilip Kota >> --- >> Changes on v2: >> Address review comments >> Update the compatible property definition >> Add description for reset-cells >> Add 'additionalProperties: false' property >> >> .../bindings/reset/intel,syscon-reset.yaml | 53 ++++++++++++++++++++++ >> 1 file changed, 53 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/reset/intel,syscon-reset.yaml >> >> diff --git a/Documentation/devicetree/bindings/reset/intel,syscon-reset.yaml b/Documentation/devicetree/bindings/reset/intel,syscon-reset.yaml >> new file mode 100644 >> index 000000000000..3403a967190a >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/reset/intel,syscon-reset.yaml >> @@ -0,0 +1,53 @@ >> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) >> +%YAML 1.2 >> +--- >> +$id: http://devicetree.org/schemas/reset/intel,syscon-reset.yaml# >> +$schema: http://devicetree.org/meta-schemas/core.yaml# >> + >> +title: Intel Lightening Mountain SoC System Reset Controller >> + >> +maintainers: >> + - Dilip Kota >> + >> +properties: >> + compatible: >> + items: >> + - const: intel,rcu-lgm >> + - const: syscon >> + >> + reg: >> + description: Reset controller register base address and size >> + >> + intel,global-reset: >> + $ref: /schemas/types.yaml#/definitions/uint32-array >> + description: Global reset register offset and bit offset. >> + >> + "#reset-cells": >> + const: 2 >> + description: | >> + The 1st cell is the register offset. >> + The 2nd cell is the bit offset in the register. >> + >> +required: >> + - compatible >> + - reg >> + - intel,global-reset >> + - "#reset-cells" >> + >> +additionalProperties: false >> + >> +examples: >> + - | >> + rcu0: reset-controller@00000000 { >> + compatible = "intel,rcu-lgm", "syscon"; >> + reg = <0x000000 0x80000>; >> + intel,global-reset = <0x10 30>; >> + #reset-cells = <2>; >> + }; >> + >> + pcie_phy0: pciephy@... { >> + ... > You need to run 'make dt_binding_check' and fix the warnings. The > example has to be buildable and it is not. Sure, i  will correct this pcie_phy0 node. But i didn't get any warnings for make dt_binding_check   CHKDT Documentation/devicetree/bindings/reset/intel,syscon-reset.yaml DTC Documentation/devicetree/bindings/arm/renesas.example.dt.yaml FATAL ERROR: Unknown output format "yaml" Will DTC report about the example node errors? But, DTC is failing with FATAL_ERROR. I tried it even after installing libyaml and headers in my local directory and export the path, but no luck.(ref: https://lkml.org/lkml/2018/12/3/951) Could you please let me know if i miss anything and help me to proceed further. Regards, Dilip > >> + /* address offset: 0x10, bit offset: 12 */ >> + resets = <&rcu0 0x10 12>; >> + ... >> + }; >> -- >> 2.11.0 >>