Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp179249yba;
        Tue, 23 Apr 2019 22:22:34 -0700 (PDT)
X-Google-Smtp-Source: APXvYqyBrIzG8296AWYgoozzEihwHVhTMvpLiYnW+rq0HdspM03dEszUNO4EAZni3l1/mRmdpnVP
X-Received: by 2002:aa7:9811:: with SMTP id e17mr2321196pfl.253.1556083354648;
        Tue, 23 Apr 2019 22:22:34 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1556083354; cv=none;
        d=google.com; s=arc-20160816;
        b=HUBFdAPxwJrpUvgErY2HoLK61lCndldoTrtqX8ivNWqgRS24zo5Fb5YrB2aTJmcpEu
         MztTjiRW1audZJv4Ju/4fBhi8RVb+KNV1f6Tl9ID99G80xO92PqA2uH4zJa2/P4uUPVE
         HA8XQpcw1VzbwSUKICTx3FPS3X/5yld3Rk+aLN8fXUDM/1k5UQPJr98zjLn7bV13LV1U
         PVil6uZfCJMM8n1ITiFcoKJhyt2lYiSutdLyipXdQE/aZ4pIwbxUcHuhrID68NsiruBr
         MW4nhibfkOQMnfdYTunGRphk/lObyWbH33o2B21/NDUfBl1eUkEjUieIEg/WTNmo9bYB
         dvSg==
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=+47SSSQi1P/1oXBgwd/uKwwchWi1ksxr6zJt5s4wu5I=;
        b=KDPG2sunRySMgPNgaB7By0k9xRKfIfkX0pvWu+vQ2b6sdx8iF8VJw6cHOO7NXafVmu
         1IQaoQ+gcHwlcDFsoZ2ddn+WjpczjO3uq2z6XXMkCaBPlsnj5Ad+cQSWZAL9iMT2TJph
         limUeTCzExjftEEYjINK7z/G1Gnj+dshKYIxNkeD9eEFQz+ALP3eiblZq/MyZIlUcyvS
         1VYNsR44NwJQsyG8BJHje/0Svtdx50gBNIeLstyIx/135vFyFIefmtRAB/LBRr6udaCX
         aPmg/m9FZGQXeeh+7gMHMQ6T/99oYfNrWctQbRZIXG/BYNZuNT0GwlCD2nALl27ozr78
         kvBw==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@nvidia.com header.s=n1 header.b=kv5YP38B;
       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 d14si17617964pgb.26.2019.04.23.22.22.19;
        Tue, 23 Apr 2019 22:22:34 -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=kv5YP38B;
       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 S1729484AbfDXFVH (ORCPT <rfc822;rao.subba.venkata@gmail.com>
        + 99 others); Wed, 24 Apr 2019 01:21:07 -0400
Received: from hqemgate15.nvidia.com ([216.228.121.64]:6615 "EHLO
        hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1725919AbfDXFVH (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 24 Apr 2019 01:21:07 -0400
Received: from hqpgpgate102.nvidia.com (Not Verified[216.228.121.13]) by hqemgate15.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA)
        id <B5cbff2290000>; Tue, 23 Apr 2019 22:20:41 -0700
Received: from hqmail.nvidia.com ([172.20.161.6])
  by hqpgpgate102.nvidia.com (PGP Universal service);
  Tue, 23 Apr 2019 22:21:06 -0700
X-PGP-Universal: processed;
        by hqpgpgate102.nvidia.com on Tue, 23 Apr 2019 22:21:06 -0700
Received: from HQMAIL108.nvidia.com (172.18.146.13) by HQMAIL107.nvidia.com
 (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 24 Apr
 2019 05:21:05 +0000
Received: from hqnvemgw02.nvidia.com (172.16.227.111) by HQMAIL108.nvidia.com
 (172.18.146.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend
 Transport; Wed, 24 Apr 2019 05:21:06 +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 <B5cbff23c0002>; Tue, 23 Apr 2019 22:21:05 -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 04/16] PCI: dwc: Perform dbi regs write lock towards the end
Date:   Wed, 24 Apr 2019 10:49:52 +0530
Message-ID: <20190424052004.6270-5-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=1556083241; bh=+47SSSQi1P/1oXBgwd/uKwwchWi1ksxr6zJt5s4wu5I=;
        h=X-PGP-Universal:From:To:CC:Subject:Date:Message-ID:X-Mailer:
         In-Reply-To:References:X-NVConfidentiality:MIME-Version:
         Content-Type;
        b=kv5YP38BhnAsB9Aee4GIzpiWvRvvJduBS1knNfT38lvVR22DVIUty5WF5ABZu/rj3
         f04mV/cgJxWdHH+gnlfumqOWBSbZAa5mAOLx/LQAPwm9eVSEVGt7HYASb/SxkbA3YG
         B3Vh9FuZ8YT0H7cbaDXTUTsLrH+0d518s2F04tKN8QVYVcTouMXnrIEFBPWzlQaovq
         zc47YCIXMNxg3i5lMTC82ppTX2yQ3JJ0XOPO+SLDvOjaycSplaMefR4EDO/XHwkogI
         n9t1bsmtRsBY+9JnNgQpV2FNyU6qMMZWdl4sQHJRdb82LJqSpp3dDkk1ovEk4Yz74R
         tO1wZE3V9pr3A==
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Remove multiple write enable and disable sequences of dbi registers as
Tegra194 implements writes to BAR-0 register (offset: 0x10) controlled by
DBI write-lock enable bit thereby not allowing any further writes to BAR-0
register in config space to take place. Hence disabling write permission
only towards the end.

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

Changes since [v3]:
* None

Changes since [v2]:
* None

Changes since [v1]:
* None

 drivers/pci/controller/dwc/pcie-designware-host.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/drivers/pci/controller/dwc/pcie-designware-host.c b/drivers/pci/controller/dwc/pcie-designware-host.c
index 36fd3f5b48f6..e5e3571dd2fe 100644
--- a/drivers/pci/controller/dwc/pcie-designware-host.c
+++ b/drivers/pci/controller/dwc/pcie-designware-host.c
@@ -654,7 +654,6 @@ void dw_pcie_setup_rc(struct pcie_port *pp)
 	val &= 0xffff00ff;
 	val |= 0x00000100;
 	dw_pcie_writel_dbi(pci, PCI_INTERRUPT_LINE, val);
-	dw_pcie_dbi_ro_wr_dis(pci);
 
 	/* Setup bus numbers */
 	val = dw_pcie_readl_dbi(pci, PCI_PRIMARY_BUS);
@@ -686,8 +685,6 @@ void dw_pcie_setup_rc(struct pcie_port *pp)
 
 	dw_pcie_wr_own_conf(pp, PCI_BASE_ADDRESS_0, 4, 0);
 
-	/* Enable write permission for the DBI read-only register */
-	dw_pcie_dbi_ro_wr_en(pci);
 	/* Program correct class for RC */
 	dw_pcie_wr_own_conf(pp, PCI_CLASS_DEVICE, 2, PCI_CLASS_BRIDGE_PCI);
 	/* Better disable write permission right after the update */
-- 
2.17.1