Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp180926yba;
        Tue, 23 Apr 2019 22:25:24 -0700 (PDT)
X-Google-Smtp-Source: APXvYqy59voKGcmEQIb5GsxDTwYYw+R6P+hV/1B5oaIvZ1GMRtOvsnvvd0FTTgcwSDOfU4HJPu85
X-Received: by 2002:a65:5086:: with SMTP id r6mr813746pgp.301.1556083524566;
        Tue, 23 Apr 2019 22:25:24 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1556083524; cv=none;
        d=google.com; s=arc-20160816;
        b=TV0Ar/tU2jkWJzOAci3/pCup+gfEcamrQtTGEtCYGTeXP6Xa2UCIxscDVZL9x2+Fcz
         0u9gaFPJrUn0PfSe8c5Zyy1EFnuf7bYofEpf87uKhtyK0wk8XgKTplGG2ps7upVVL3BM
         e7uiONBqjod/NyWXyhi1Mh48KKP2k31c+ObznAwxthNJig79LQOG2bDsC4tY8xvN/FwG
         lsFQ2cMDa+wFvl9WemZ0aLd/gQJidXMSuyI6Q++7HE/dStXFAjl6dQaENUWt7eSoDktq
         xgQ/D99tC9f17XrbXWvtOepy1z3i7Yf4DhwwxdphgBem9i+hacZTW53dSpfli2JKd6e7
         l6PA==
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=qibkayiBTsmava78mLScJfeUOO8heym5bdM8wviVGvc=;
        b=xf+2yBHrNjAT5X8ZUOvKbKg2dvuR2YNB2CpNwnR+Em3fBapSwduWKY4t+trpIspmqM
         zo8ApmMi0nh21++7ics9Ddk1PldGA5wTGlMSfpTPg37gszvg3WstRQV/GHbJQew7MNVm
         TWQgqP24B7V5LEWv+h5+sGw7S3R2ZfTRNqlntN4v/H/0AnEjXU+zCC6n8ash1PNtLK2u
         i8gOAcZbIAw+BEqLBf/LhMhAoqjuZzXqkIlS7zQ86D7g3VACs4lRnODR9/M86SVm5Zlr
         BRreSmH+sEgLYhJzu3wfKAxG9496fB0xfTNjla0sQJAVkQn+kM/MIPjJqF0io795hxW4
         byqQ==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@nvidia.com header.s=n1 header.b=gl0YGnC7;
       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 a3si17892183pfc.276.2019.04.23.22.25.09;
        Tue, 23 Apr 2019 22:25:24 -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=gl0YGnC7;
       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 S1729614AbfDXFW2 (ORCPT <rfc822;rao.subba.venkata@gmail.com>
        + 99 others); Wed, 24 Apr 2019 01:22:28 -0400
Received: from hqemgate16.nvidia.com ([216.228.121.65]:18469 "EHLO
        hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1726151AbfDXFW2 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 24 Apr 2019 01:22:28 -0400
Received: from hqpgpgate101.nvidia.com (Not Verified[216.228.121.13]) by hqemgate16.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA)
        id <B5cbff2900000>; Tue, 23 Apr 2019 22:22:24 -0700
Received: from hqmail.nvidia.com ([172.20.161.6])
  by hqpgpgate101.nvidia.com (PGP Universal service);
  Tue, 23 Apr 2019 22:22:27 -0700
X-PGP-Universal: processed;
        by hqpgpgate101.nvidia.com on Tue, 23 Apr 2019 22:22:27 -0700
Received: from HQMAIL106.nvidia.com (172.18.146.12) by HQMAIL104.nvidia.com
 (172.18.146.11) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 24 Apr
 2019 05:22:27 +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:27 +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 <B5cbff28e0001>; Tue, 23 Apr 2019 22:22:26 -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 09/16] Documentation/devicetree: Add PCIe supports-clkreq property
Date:   Wed, 24 Apr 2019 10:49:57 +0530
Message-ID: <20190424052004.6270-10-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=1556083344; bh=qibkayiBTsmava78mLScJfeUOO8heym5bdM8wviVGvc=;
        h=X-PGP-Universal:From:To:CC:Subject:Date:Message-ID:X-Mailer:
         In-Reply-To:References:X-NVConfidentiality:MIME-Version:
         Content-Type;
        b=gl0YGnC7a4Tf6VHkfGwdQKPokbwBybw3hU7b+WSvpuGiSrab/nBcC9WE5P9VsudUJ
         /o1jO1I6EW9itaoz5zPF6fjPq/JwcloBmVz7chnNcEDZ7NumFlzSrRUmw6F7F5RHtX
         JNutmk+7ay8mJxrBYqSwIdqsYZLxHicYxzw57pS47KX7db3jatnjjDHgTwM9yo1y9h
         sbs1TyVEVlPIA6hb9DFLTHmqTk9Ihezgi1qUWl6nxm6M0ATQoQ4B1VZCkMk9bMWXcw
         UTb4ANZV6BMk7WWIteewaLja607woCltAsJkxt3SZZnqpPtBhQuhzoftQaG6SpRS8C
         Pbf6pDjGPXJ6w==
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Some host controllers need to know the existence of clkreq signal routing to
downstream devices to be able to advertise low power features like ASPM L1
substates. Without clkreq signal routing being present, enabling ASPM L1 sub
states might lead to downstream devices falling off the bus. Hence a new device
tree property 'supports-clkreq' is added to make such host controllers
aware of clkreq signal routing to downstream devices.

Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
---
Changes since [v4]:
* None

Changes since [v3]:
* Rebased on top of linux-next top of the tree

Changes since [v2]:
* None

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

 Documentation/devicetree/bindings/pci/pci.txt | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/Documentation/devicetree/bindings/pci/pci.txt b/Documentation/devicetree/bindings/pci/pci.txt
index 92c01db610df..d132f9efeb3e 100644
--- a/Documentation/devicetree/bindings/pci/pci.txt
+++ b/Documentation/devicetree/bindings/pci/pci.txt
@@ -24,6 +24,11 @@ driver implementation may support the following properties:
    unsupported link speed, for instance, trying to do training for
    unsupported link speed, etc.  Must be '4' for gen4, '3' for gen3, '2'
    for gen2, and '1' for gen1. Any other values are invalid.
+- supports-clkreq:
+   If present this property specifies that CLKREQ signal routing exists from
+   root port to downstream device and host bridge drivers can do programming
+   which depends on CLKREQ signal existence. For example, programming root port
+   not to advertise ASPM L1 Sub-States support if there is no CLKREQ signal.
 
 PCI-PCI Bridge properties
 -------------------------
-- 
2.17.1