From patchwork Tue Jan 14 10:47:10 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Ramuthevar, Vadivel MuruganX" X-Patchwork-Id: 1222676 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (no SPF record) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=devicetree-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.intel.com Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 47xnGG2SnMz9sPW for ; Tue, 14 Jan 2020 21:47:17 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726169AbgANKrQ (ORCPT ); Tue, 14 Jan 2020 05:47:16 -0500 Received: from mga06.intel.com ([134.134.136.31]:15619 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726044AbgANKrP (ORCPT ); Tue, 14 Jan 2020 05:47:15 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Jan 2020 02:47:15 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,432,1571727600"; d="scan'208";a="248013848" Received: from sgsxdev004.isng.intel.com (HELO localhost) ([10.226.88.13]) by fmsmga004.fm.intel.com with ESMTP; 14 Jan 2020 02:47:12 -0800 From: "Ramuthevar,Vadivel MuruganX" To: linux-kernel@vger.kernel.org, robh@kernel.org Cc: kishon@ti.com, devicetree@vger.kernel.org, cheol.yong.kim@intel.com, andriy.shevchenko@intel.com, qi-ming.wu@intel.com, Ramuthevar Vadivel Murugan Subject: [PATCH v1] dt-bindings: phy: Fix for intel, lgm-emmc-phy.yaml build error Date: Tue, 14 Jan 2020 18:47:10 +0800 Message-Id: <20200114104710.23135-1-vadivel.muruganx.ramuthevar@linux.intel.com> X-Mailer: git-send-email 2.11.0 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org From: Ramuthevar Vadivel Murugan This patch fixes the devicetree binding yaml build errors in linux-next kernel Error: Documentation/devicetree/bindings/ phy/intel,lgm-emmc-phy.example.dts:21.19-20 syntax error FATAL ERROR: Unable to parse input tree Signed-off-by: Ramuthevar Vadivel Murugan Reported-by: Rob Herring --- .../devicetree/bindings/phy/intel,lgm-emmc-phy.yaml | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml b/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml index ff7959c21af0..d9bd2e47dfe7 100644 --- a/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml +++ b/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml @@ -16,10 +16,7 @@ description: |+ The eMMC PHY node should be the child of a syscon node with the required property: - - compatible: Should be one of the following: - "intel,lgm-syscon", "syscon" - - reg: - maxItems: 1 + should be compatible strings are - "intel,lgm-syscon", "syscon" properties: compatible: @@ -34,6 +31,12 @@ properties: clocks: maxItems: 1 + "#address-cells": + const: 1 + + "#size-cells": + const: 1 + required: - "#phy-cells" - compatible @@ -45,8 +48,10 @@ examples: sysconf: chiptop@e0200000 { compatible = "intel,lgm-syscon", "syscon"; reg = <0xe0200000 0x100>; + #address-cells = <1>; + #size-cells = <1>; - emmc-phy: emmc-phy@a8 { + emmc_phy: emmc_phy@a8 { compatible = "intel,lgm-emmc-phy"; reg = <0x00a8 0x10>; clocks = <&emmc>;