Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3322093yba;
        Tue, 23 Apr 2019 01:31:39 -0700 (PDT)
X-Google-Smtp-Source: APXvYqyjdU/tHlU1wHSQIqzYt/u0yiYL/d/Dy0HyUibIy2pDvOnJsrnqxZDBBg/e99nV4reeACtP
X-Received: by 2002:a65:5304:: with SMTP id m4mr23226960pgq.281.1556008299917;
        Tue, 23 Apr 2019 01:31:39 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1556008299; cv=none;
        d=google.com; s=arc-20160816;
        b=WpW04X+SAAObka+ksAlXMBKZ9lPFS+gTVRwU+4g0GqGEw1qT1M70u2qP3HFCOrV3qW
         U3K5K3nU7Q/oWqtxmbAw8xciK5swI13wJdtummBKcsrry8ySuhpXaL8deLk8yO3CU+HZ
         zgpBYl/TXjSRcPkOAqzny3p/kUWBYCAJUgtYQzeHthp4oHaDNGJtXLgAroc0Xu/kXay1
         0G36+oDi+mbq/cV5uX+DSTYt0WFNml3hAez14+y9TfH13+yk64ypo4DquHD5z4/m/tf/
         ObubTXAdnSNeI9eMYq7wyfmt60rfY6AOxLKAE8n70d2vZztvZ4At08g01GdbMCtUl0GH
         CuXg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:sender:dkim-signature:mime-version:references
         :in-reply-to:message-id:date:subject:cc:to:from;
        bh=e4y3GVwYyoc5tTHi1u0vhFYjXSAjhOmxVmDxHjTavBk=;
        b=C2zLGod8fHrjsb4OCbWsRgOwXxAjkeRLnJS+4+4cYewmCC2yy7aPUh33yomnem6iyS
         KauA2jmcwkxa8wvC72Ep+CYFL3Yu7joLmRDtSMcp8bVpMTQ4OL9klRChqvhmt/qnYQYJ
         SdI08+cuLXL0C3QWLNurz7YKVIf/1zHIYcRmKU8gtsTRoxxAMjvVQfX+JxHzhwUprffd
         WK0dETgNLAcpTXdyQK91bc+pUEsSEq9+lSiGEVfLUIQL4nV35d22Tqk0+1vt5Z3/DZG8
         0CeLw7vSKNnQCpsvbtik7gCBqiSigv3lXqSceE02rNqO40HK7jWl3ZbYYoXdyoqFH+mZ
         IevQ==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@nvidia.com header.s=n1 header.b=J4QWw+fV;
       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=nvidia.com
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67])
        by mx.google.com with ESMTP id b8si15913808pla.153.2019.04.23.01.31.24;
        Tue, 23 Apr 2019 01:31:39 -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=@nvidia.com header.s=n1 header.b=J4QWw+fV;
       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=nvidia.com
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1727165AbfDWI24 (ORCPT <rfc822;mailist1go@gmail.com>
        + 99 others); Tue, 23 Apr 2019 04:28:56 -0400
Received: from hqemgate15.nvidia.com ([216.228.121.64]:6696 "EHLO
        hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1727105AbfDWI2z (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 23 Apr 2019 04:28:55 -0400
Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate15.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA)
        id <B5cbeccad0001>; Tue, 23 Apr 2019 01:28:29 -0700
Received: from hqmail.nvidia.com ([172.20.161.6])
  by hqpgpgate101.nvidia.com (PGP Universal service);
  Tue, 23 Apr 2019 01:28:54 -0700
X-PGP-Universal: processed;
        by hqpgpgate101.nvidia.com on Tue, 23 Apr 2019 01:28:54 -0700
Received: from HQMAIL107.nvidia.com (172.20.187.13) by HQMAIL105.nvidia.com
 (172.20.187.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 23 Apr
 2019 08:28:54 +0000
Received: from hqnvemgw02.nvidia.com (172.16.227.111) by HQMAIL107.nvidia.com
 (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend
 Transport; Tue, 23 Apr 2019 08:28:53 +0000
Received: from vidyas-desktop.nvidia.com (Not Verified[10.24.37.38]) by hqnvemgw02.nvidia.com with Trustwave SEG (v7,5,8,10121)
        id <B5cbeccc00004>; Tue, 23 Apr 2019 01:28:53 -0700
From:   Vidya Sagar <vidyas@nvidia.com>
To:     <lorenzo.pieralisi@arm.com>, <bhelgaas@google.com>,
        <robh+dt@kernel.org>, <mark.rutland@arm.com>,
        <thierry.reding@gmail.com>, <jonathanh@nvidia.com>,
        <kishon@ti.com>, <catalin.marinas@arm.com>, <will.deacon@arm.com>,
        <jingoohan1@gmail.com>, <gustavo.pimentel@synopsys.com>
CC:     <mperttunen@nvidia.com>, <linux-pci@vger.kernel.org>,
        <devicetree@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>, <kthota@nvidia.com>,
        <mmaddireddy@nvidia.com>, <vidyas@nvidia.com>, <sagar.tv@gmail.com>
Subject: [PATCH V4 11/16] dt-bindings: PHY: P2U: Add Tegra 194 P2U block
Date:   Tue, 23 Apr 2019 13:57:25 +0530
Message-ID: <20190423082730.370-12-vidyas@nvidia.com>
X-Mailer: git-send-email 2.17.1
In-Reply-To: <20190423082730.370-1-vidyas@nvidia.com>
References: <20190423082730.370-1-vidyas@nvidia.com>
X-NVConfidentiality: public
MIME-Version: 1.0
Content-Type: text/plain
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1;
        t=1556008110; bh=e4y3GVwYyoc5tTHi1u0vhFYjXSAjhOmxVmDxHjTavBk=;
        h=X-PGP-Universal:From:To:CC:Subject:Date:Message-ID:X-Mailer:
         In-Reply-To:References:X-NVConfidentiality:MIME-Version:
         Content-Type;
        b=J4QWw+fV0RvnybZU6GbmU1AMWq1RkubFo89y3LcGoDtoNnxn2ywPZMcRwjQtxPtxl
         GwGPzUJQOK7LicSAoj3Nv961zzlqqxpdt2VOiaA6CWGjpNuVhRjf99+frOwwXoCd4z
         83RAej1WJUgA449HBWHDPVHHh/lSh19FuFGxw9TthidoCC/BRGbzXRhbVqi0Ed1evR
         wpNfCqikiSSbYDbaO7pvFPte6ejYz5r6D95Kx1tOjeVA7RssiyQwD9mAPIkQVa3/8I
         6qPHFlUc/XpMjZo+9aK9sBA5HOJ1mjOCukvg3ZCoJW+jutDAL6RollZyTGMv6dagWq
         4rFlPS7vB3FpA==
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Add support for Tegra194 P2U (PIPE to UPHY) module block which is a glue
module instantiated one for each PCIe lane between Synopsys Designware core
based PCIe IP and Universal PHY block.
---
Changes since [v3]:
* None

Changes since [v2]:
* Changed node label to reflect new format that includes either 'hsio' or
  'nvhs' in its name to reflect which UPHY brick they belong to

Changes since [v1]:
* This is a new patch in v2 series

 .../bindings/phy/phy-tegra194-p2u.txt         | 28 +++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/phy/phy-tegra194-p2u.txt

diff --git a/Documentation/devicetree/bindings/phy/phy-tegra194-p2u.txt b/Documentation/devicetree/bindings/phy/phy-tegra194-p2u.txt
new file mode 100644
index 000000000000..8b543cba483b
--- /dev/null
+++ b/Documentation/devicetree/bindings/phy/phy-tegra194-p2u.txt
@@ -0,0 +1,28 @@
+NVIDIA Tegra194 P2U binding
+
+Tegra194 has two PHY bricks namely HSIO (High Speed IO) and NVHS (NVIDIA High
+Speed) each interfacing with 12 and 8 P2U instances respectively.
+A P2U instance is a glue logic between Synopsys DesignWare Core PCIe IP's PIPE
+interface and PHY of HSIO/NVHS bricks. Each P2U instance represents one PCIe
+lane.
+
+Required properties:
+- compatible: For Tegra19x, must contain "nvidia,tegra194-p2u".
+- reg: Should be the physical address space and length of respective each P2U
+       instance.
+- reg-names: Must include the entry "ctl".
+
+Required properties for PHY port node:
+- #phy-cells: Defined by generic PHY bindings.  Must be 0.
+
+Refer to phy/phy-bindings.txt for the generic PHY binding properties.
+
+Example:
+
+p2u_hsio_0: p2u@3e10000 {
+	compatible = "nvidia,tegra194-p2u";
+	reg = <0x03e10000 0x10000>;
+	reg-names = "ctl";
+
+	#phy-cells = <0>;
+};
-- 
2.17.1