Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3493146yba;
        Tue, 16 Apr 2019 12:30:23 -0700 (PDT)
X-Google-Smtp-Source: APXvYqygzqxW17q79KRv3PySZ2gUYEYPAieSPo7my9DvZeCWkkCgTB61kZ4BPREhvrXnvkEfxAo0
X-Received: by 2002:a17:902:2a03:: with SMTP id i3mr84789986plb.229.1555443023036;
        Tue, 16 Apr 2019 12:30:23 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1555443023; cv=none;
        d=google.com; s=arc-20160816;
        b=Izzv191rjFo6fFFByQtEKqhyTAyLOF0295Z/RIFF/ERQjlN2cS1vcYGrCf0TDP2eZ1
         dFECfh+ijgykBecVZyjMOlDGojqwwD9+1MNebNn8MCY1t6I9u2xDgovt0k8k3rwQKeMg
         yJ+qy8bBtM+8mP8P45+jXHuLMWYvYfb6xsjdhNDCmbza4csNtrg+9fOka+2YYbSuq7H8
         efJ6MtWrUgoEn/5T5G2SvUQ0wTBO7ilgMe4+rexvwRoLN9oNV/8uXzM6HiLVgvedNHWD
         hl0IRV5adRJhHaW6oVH7rzMJhlZ9rZ9hzYJjj3vVDz2DduCc65K09L4eoScm6g/bmdqR
         HujA==
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=PtKGFQLBelxa/+FjhBjQK4lGsc99ji+teoNNxGLSwOs=;
        b=YbySXkGhUP4RIOaLxXi/5IPdXClvx5ggzkM0hnMpg0CmP1ViydNj/ERt6big7YJu3/
         7Fd0H/JBCyayfL47sQTAqPxp6hN4TPbrRtiS28z4nfbz6G9X+VHPNEA8CpSDbird8X0p
         KQsdqZHNhQhnAtqGh4PiodjsOHkELyacHYonMVlJQ2vEzkJifn0xZdbmeF6bEZ4hyByr
         eNQ1Ffva7KqxNq1Fl6v1MCV9NQ1EpOJ8a01E6Z0ZQTUSLbaf/L0jLQ9TX9hyOSsMM+Pe
         gW9Gtbp9ao/QadWonwNnq9sUy/sesE0Ufzi6QvIIk98krdDWQ/15tH7y6V5yqx8PbVEk
         PPXw==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@nvidia.com header.s=n1 header.b=mDqXOMRN;
       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 r15si32726148pfn.4.2019.04.16.12.30.07;
        Tue, 16 Apr 2019 12:30:23 -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=mDqXOMRN;
       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 S1730513AbfDPT3D (ORCPT <rfc822;rruigrok1@gmail.com> + 99 others);
        Tue, 16 Apr 2019 15:29:03 -0400
Received: from hqemgate14.nvidia.com ([216.228.121.143]:12109 "EHLO
        hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1727180AbfDPT3B (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 16 Apr 2019 15:29:01 -0400
Received: from hqpgpgate102.nvidia.com (Not Verified[216.228.121.13]) by hqemgate14.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA)
        id <B5cb62d010003>; Tue, 16 Apr 2019 12:29:05 -0700
Received: from hqmail.nvidia.com ([172.20.161.6])
  by hqpgpgate102.nvidia.com (PGP Universal service);
  Tue, 16 Apr 2019 12:29:00 -0700
X-PGP-Universal: processed;
        by hqpgpgate102.nvidia.com on Tue, 16 Apr 2019 12:29:00 -0700
Received: from HQMAIL106.nvidia.com (172.18.146.12) by HQMAIL105.nvidia.com
 (172.20.187.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 16 Apr
 2019 19:29:00 +0000
Received: from hqnvemgw01.nvidia.com (172.20.150.20) by HQMAIL106.nvidia.com
 (172.18.146.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend
 Transport; Tue, 16 Apr 2019 19:28:59 +0000
Received: from vidyas-desktop.nvidia.com (Not Verified[10.24.37.38]) by hqnvemgw01.nvidia.com with Trustwave SEG (v7,5,8,10121)
        id <B5cb62cf70001>; Tue, 16 Apr 2019 12:28:59 -0700
From:   Vidya Sagar <vidyas@nvidia.com>
To:     <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>, <lorenzo.pieralisi@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 V3 11/16] dt-bindings: PHY: P2U: Add Tegra 194 P2U block
Date:   Wed, 17 Apr 2019 00:57:25 +0530
Message-ID: <20190416192730.15681-12-vidyas@nvidia.com>
X-Mailer: git-send-email 2.17.1
In-Reply-To: <20190416192730.15681-1-vidyas@nvidia.com>
References: <20190416192730.15681-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=1555442945; bh=PtKGFQLBelxa/+FjhBjQK4lGsc99ji+teoNNxGLSwOs=;
        h=X-PGP-Universal:From:To:CC:Subject:Date:Message-ID:X-Mailer:
         In-Reply-To:References:X-NVConfidentiality:MIME-Version:
         Content-Type;
        b=mDqXOMRNUp0Byd9Lue9gqfJMYYYjc+bUkI9o+Yp3hqCc2W3C0EIwO9OmfDrs7RpTH
         HSTQ0ZL2cDctx8zVojdhAv/Pxm0YIfa0feT5zsxL5OsY9sQ+4A0VbDFHR3F+BFgjj7
         34mHXjj8UjP1QJoc6VWXANGNaVBPnEAlSYJuuFBllGbfT8UukDcXr/r2zEDhaXd6hP
         do+uvITF2Ked4YglhzRydq0wPXj93PKW4FXYKHeCzwWnO2FLeALXGxcyw35CqHUVvb
         Aa5scZeowlJoj9qCNVi2uW/TsxJKFvAF5iNAtEztmMLySnKyMy+9AuoYtUYw1RVQzb
         WqTGho2Xh80tg==
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 [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