Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp114038ybl; Tue, 10 Dec 2019 18:51:07 -0800 (PST) X-Google-Smtp-Source: APXvYqyqKtiHWZGfuDOL5Im9C2lRcnuYYm6cYUBH6IHHAB9f+dZXujGydtBG4/61ckn/Uv/zHIbS X-Received: by 2002:a05:6830:1d6:: with SMTP id r22mr786986ota.196.1576032667696; Tue, 10 Dec 2019 18:51:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576032667; cv=none; d=google.com; s=arc-20160816; b=YPAmuBFYdMSlA9WxYDwX/KJIm6nvl+YRBdGbkdCTc8aebjSuge6LScYIb+vgdXRaOL aS5ZNvdjb3Kx29rmm4GLauJyXrojU/2HkBN9AedRgqdPk9fBRR3RAUa28CdIcMNCtYF5 5uACL8oGvYGt7gcrXyAvd41eE7we3yeVHwCMPo/PXzirsbzBVIKmVWQhQmmeB7eyusWI NdUF1IsfjKNCC0CXTDRDbZ/MYhodRGO/ksJYTFATJv20lTEG7b/htLuFlMq20fnoIfnZ 5T5TfTPuR1lT7QTTaxKx6VozRtNKu9cFig6DL4D1e7Uj+MVpcUv/KLL4SgRJC7EOehaF FL1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=Nrw7zZGSXxB9VMoj4fMPddPfyHnu73DOSgawClxtdKE=; b=NpQrNPsdTRMQVmqZEvpVrqV5LMCqceTcSMnJvNlkIUo8P7eDD/k9pxEcpiL5CnLxHU 7yHgw297gH/TqUQJehKCXhLipU8V0kA83RyZJILf72sIZVWsgbGL6VKt0VKg/XiDkf2M RTCayzxuE+EutybZ6uNuNvP7Djk0DRDXFRyG2fgFvespbSSwJC6/mYia983owk9BOlcY Wlo3vXG2GqrM/HtZbZ25rculYRpm+bG4PVpY5fn+Tk39nquUuiM16Y0QyWTnjLRKzbDR hEGKLrjGVnr82SB/laVJzUfQMBuVFdMrLEBaglbccVFYQ6UWAK8U020Wt6TJlY1xmK+/ x2Vg== 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 m26si208635otn.307.2019.12.10.18.50.55; Tue, 10 Dec 2019 18:51:07 -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; 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 S1727610AbfLKCuY (ORCPT + 99 others); Tue, 10 Dec 2019 21:50:24 -0500 Received: from mga04.intel.com ([192.55.52.120]:55267 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726619AbfLKCuY (ORCPT ); Tue, 10 Dec 2019 21:50:24 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Dec 2019 18:50:23 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,301,1571727600"; d="scan'208";a="225360141" Received: from sgsxdev004.isng.intel.com (HELO localhost) ([10.226.88.13]) by orsmga002.jf.intel.com with ESMTP; 10 Dec 2019 18:50:19 -0800 From: "Ramuthevar,Vadivel MuruganX" To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, kishon@ti.com Cc: andriy.shevchenko@intel.com, cheol.yong.kim@intel.com, qi-ming.wu@intel.com, peter.harliman.liem@intel.com, Ramuthevar Vadivel Murugan Subject: [PATCH v7 1/2] dt-bindings: phy: intel-emmc-phy: Add YAML schema for LGM eMMC PHY Date: Wed, 11 Dec 2019 10:50:10 +0800 Message-Id: <20191211025011.12156-2-vadivel.muruganx.ramuthevar@linux.intel.com> X-Mailer: git-send-email 2.11.0 In-Reply-To: <20191211025011.12156-1-vadivel.muruganx.ramuthevar@linux.intel.com> References: <20191211025011.12156-1-vadivel.muruganx.ramuthevar@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Ramuthevar Vadivel Murugan Add a YAML schema to use the host controller driver with the eMMC PHY on Intel's Lightning Mountain SoC. Signed-off-by: Ramuthevar Vadivel Murugan --- .../bindings/phy/intel,lgm-emmc-phy.yaml | 62 ++++++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml diff --git a/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml b/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml new file mode 100644 index 000000000000..aed11258d96d --- /dev/null +++ b/Documentation/devicetree/bindings/phy/intel,lgm-emmc-phy.yaml @@ -0,0 +1,62 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/phy/intel,lgm-emmc-phy.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Intel Lightning Mountain(LGM) eMMC PHY Device Tree Bindings + +maintainers: + - Ramuthevar Vadivel Murugan + +description: |+ + Bindings for eMMC PHY on Intel's Lightning Mountain SoC, syscon + node is used to reference the base address of eMMC phy registers. + + 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 + +properties: + compatible: + contains: + const: intel,lgm-emmc-phy + + "#phy-cells": + const: 0 + + reg: + maxItems: 1 + + clocks: + maxItems: 1 + + clock-names: + maxItems: 1 + +required: + - "#phy-cells" + - compatible + - reg + - clocks + - clock-names + +examples: + - | + sysconf: chiptop@e0200000 { + compatible = "intel,lgm-syscon", "syscon"; + reg = <0xe0200000 0x100>; + + emmc-phy: emmc-phy@a8 { + compatible = "intel,lgm-emmc-phy"; + reg = <0x00a8 0x10>; + clocks = <&emmc>; + clock-names = "emmcclk"; + #phy-cells = <0>; + }; + }; +... -- 2.11.0