Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp181248yba;
        Tue, 23 Apr 2019 22:25:51 -0700 (PDT)
X-Google-Smtp-Source: APXvYqxDHtZSqFkkYSOtg+k+SfJBfaNY/tnXPPP2+QW9wtTuVudZt5cI2WtywnTIkivnUj5C8lPk
X-Received: by 2002:a63:2015:: with SMTP id g21mr28259807pgg.226.1556083551768;
        Tue, 23 Apr 2019 22:25:51 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1556083551; cv=none;
        d=google.com; s=arc-20160816;
        b=FOLJGabV3zsgEmMOeqoR/r8fSO09APkL5qkXDsviv9itf1jzBFwgX/gTfbmYGge2Hq
         EOUfmEd9onstq2+j6kMe3h4RCyyOlDwg5/xGPZKEmj3z7XTJz0y21swks0hTAxfNUwMR
         ZqdeGvn3MKUcbXNjJ98bHtzvBYA+A/xwQBYT8C1zf6vSnXpJ6gWYL9laJw4HIebuZJSP
         O1Dnf3SgOKjqH2IPXdfzzLSrEJ5VhAjDOA8JWRZPQ1RpCaOP+FT3Z/rVKwHklLjRzdqX
         0aVXwdVA7s47hG4MpE3MQB/pdcxpd9vgkrBjWoh2m1LSbNTrvN7Ew4sv4ZnDE9X+Cjz4
         wZeQ==
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=36wPqCC9trDiNT5wTNjflw534xr32+kiByeOguTxus8=;
        b=GnMR0Ljedvu1RMVZUz2aAjDUEWXY9WUU9UKZj1cpHmxXbKFgXoceLO4Z7QUGhBmYEa
         KnmPmKBZVTPHyMuxyhkSMmJJYcZCRk9D9pcFXgjy+aHTx6llM5iTVzt0ZoP9EE4uMVY3
         da4u8sFDZFrmc6LlMiJsW3UtfZcmuZFf9WtNza4SJpF2EodyPA+friroOLld/WlhNU7/
         oTSwCepPjV6AmHTAIZEkIl652Bk40jpsFPK2CHPsLbuQU2FfOQskOJ0KmVtkVbQECw5V
         JfiYl2kTPeOFa+ie3A6adq2D4ClhXXcMp/vQlwguQTeLbokVaSyTZHJY9U9PNV1JBGys
         0xVQ==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@nvidia.com header.s=n1 header.b=qZpC90y5;
       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 y12si5414887pgp.109.2019.04.23.22.25.36;
        Tue, 23 Apr 2019 22:25:51 -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=qZpC90y5;
       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 S1729638AbfDXFW4 (ORCPT <rfc822;rao.subba.venkata@gmail.com>
        + 99 others); Wed, 24 Apr 2019 01:22:56 -0400
Received: from hqemgate14.nvidia.com ([216.228.121.143]:5751 "EHLO
        hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1726451AbfDXFW4 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 24 Apr 2019 01:22:56 -0400
Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate14.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA)
        id <B5cbff2b50000>; Tue, 23 Apr 2019 22:23:01 -0700
Received: from hqmail.nvidia.com ([172.20.161.6])
  by hqpgpgate101.nvidia.com (PGP Universal service);
  Tue, 23 Apr 2019 22:22:55 -0700
X-PGP-Universal: processed;
        by hqpgpgate101.nvidia.com on Tue, 23 Apr 2019 22:22:55 -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; Wed, 24 Apr
 2019 05:22:54 +0000
Received: from hqnvemgw02.nvidia.com (172.16.227.111) by HQMAIL106.nvidia.com
 (172.18.146.12) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend
 Transport; Wed, 24 Apr 2019 05:22:54 +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 <B5cbff2a90000>; Tue, 23 Apr 2019 22:22:54 -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 V5 11/16] dt-bindings: PHY: P2U: Add Tegra 194 P2U block
Date:   Wed, 24 Apr 2019 10:49:59 +0530
Message-ID: <20190424052004.6270-12-vidyas@nvidia.com>
X-Mailer: git-send-email 2.17.1
In-Reply-To: <20190424052004.6270-1-vidyas@nvidia.com>
References: <20190424052004.6270-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=1556083381; bh=36wPqCC9trDiNT5wTNjflw534xr32+kiByeOguTxus8=;
        h=X-PGP-Universal:From:To:CC:Subject:Date:Message-ID:X-Mailer:
         In-Reply-To:References:X-NVConfidentiality:MIME-Version:
         Content-Type;
        b=qZpC90y5wHB+FmxwKx7IJr0XEVcyRXmHiClmUHpmM0weajorg5q3STEGiiS9kEjPa
         zaYmqRgUA0KIUDe9nK0XV2Oo8A/0k4BKgyzbivW2yxPV8sHEgdrrklO2Iw/qwIawPA
         wpOUq9fhpTfJmNwTHH9uBIVMV4RRIlfR4elRTx0RfH1DyQutMFqegWiNTpWdpQ5JB0
         B7a4Oo7kOLbwyMAYjb8LZMhgdmbiSMyMH1KAvHXxW8kBHhJi9embB3de0nFEP3YRWt
         7CV4xX5Rqpo9mvzNwsiNNwaHxsEwo5DvDfBYTpMACKjcW3ne7SgfUHtlelQ2djZoA2
         X1ttiqlSw5Ktg==
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 [v4]:
* None

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