Devicetree
 help / color / mirror / Atom feed
From: Vidya Sagar <vidyas@nvidia.com>
To: treding@nvidia.com, bhelgaas@google.com
Cc: linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org,
	kthota@nvidia.com, mmaddireddy@nvidia.com, vidyas@nvidia.com,
	robh+dt@kernel.org, devicetree@vger.kernel.org
Subject: [PATCH V2 7/7] ARM64: tegra: limit PCIe config space mapping to 4K for T186
Date: Mon, 23 Oct 2017 20:05:12 +0530	[thread overview]
Message-ID: <1508769312-12465-8-git-send-email-vidyas@nvidia.com> (raw)
In-Reply-To: <1508769312-12465-1-git-send-email-vidyas@nvidia.com>

reduces PCIe config space mapping size from its current 256MB
to 4K to have only 4K of virtual memory mapping and to be
in line with driver implementation

Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
---
 arch/arm64/boot/dts/nvidia/tegra186.dtsi | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/arch/arm64/boot/dts/nvidia/tegra186.dtsi b/arch/arm64/boot/dts/nvidia/tegra186.dtsi
index 7c3a2bdd4644..c64550c32d72 100644
--- a/arch/arm64/boot/dts/nvidia/tegra186.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra186.dtsi
@@ -361,7 +361,7 @@
 		device_type = "pci";
 		reg = <0x0 0x10003000 0x0 0x00000800   /* PADS registers */
 		       0x0 0x10003800 0x0 0x00000800   /* AFI registers */
-		       0x0 0x40000000 0x0 0x10000000>; /* configuration space */
+		       0x0 0x40000000 0x0 0x00001000>; /* configuration space */
 		reg-names = "pads", "afi", "cs";
 
 		interrupts = <GIC_SPI 72 IRQ_TYPE_LEVEL_HIGH>, /* controller interrupt */
@@ -379,9 +379,9 @@
 		ranges = <0x82000000 0 0x10000000 0x0 0x10000000 0 0x00001000   /* port 0 configuration space */
 			  0x82000000 0 0x10001000 0x0 0x10001000 0 0x00001000   /* port 1 configuration space */
 			  0x82000000 0 0x10004000 0x0 0x10004000 0 0x00001000   /* port 2 configuration space */
-			  0x81000000 0 0x0        0x0 0x50000000 0 0x00010000   /* downstream I/O (64 KiB) */
-			  0x82000000 0 0x50100000 0x0 0x50100000 0 0x07F00000   /* non-prefetchable memory (127 MiB) */
-			  0xc2000000 0 0x58000000 0x0 0x58000000 0 0x28000000>; /* prefetchable memory (640 MiB) */
+			  0x81000000 0 0x0        0x0 0x40001000 0 0x00010000   /* downstream I/O (64 KiB) */
+			  0x82000000 0 0x40100000 0x0 0x40100000 0 0x07F00000   /* non-prefetchable memory (127 MiB) */
+			  0xc2000000 0 0x48000000 0x0 0x48000000 0 0x38000000>; /* prefetchable memory (896 MiB) */
 
 		clocks = <&bpmp TEGRA186_CLK_AFI>,
 			 <&bpmp TEGRA186_CLK_PCIE>,
-- 
2.7.4

      parent reply	other threads:[~2017-10-23 14:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 14:35 [PATCH V2 0/7] Tegra PCIe end point config space map code refactoring Vidya Sagar
     [not found] ` <1508769312-12465-1-git-send-email-vidyas-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2017-10-23 14:35   ` [PATCH V2 1/7] PCI: tegra: refactor config space mapping code Vidya Sagar
2017-10-23 14:35   ` [PATCH V2 2/7] ARM: tegra: limit PCIe config space mapping to 4K for T20 Vidya Sagar
2017-10-23 14:35   ` [PATCH V2 3/7] ARM: tegra: limit PCIe config space mapping to 4K for T30 Vidya Sagar
2017-10-23 14:35   ` [PATCH V2 4/7] ARM: tegra: limit PCIe config space mapping to 4K for T124 Vidya Sagar
2017-10-23 14:35   ` [PATCH V2 5/7] ARM64: tegra: limit PCIe config space mapping to 4K for T132 Vidya Sagar
2017-10-23 14:35   ` [PATCH V2 6/7] ARM64: tegra: limit PCIe config space mapping to 4K for T210 Vidya Sagar
2017-10-23 15:10   ` [PATCH V2 0/7] Tegra PCIe end point config space map code refactoring Rob Herring
     [not found]     ` <CAL_Jsq+3UAwk5gNgh=s6O1f-MadyGCtADX7pyzX8eUfBqboRfA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-23 15:24       ` Vidya Sagar
2017-10-23 16:16         ` Mikko Perttunen
     [not found]           ` <1c898f3e-582f-27fe-7e01-f52a8b8ad538-/1wQRMveznE@public.gmane.org>
2017-10-23 17:13             ` Vidya Sagar
2017-10-23 14:35 ` Vidya Sagar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1508769312-12465-8-git-send-email-vidyas@nvidia.com \
    --to=vidyas@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kthota@nvidia.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mmaddireddy@nvidia.com \
    --cc=robh+dt@kernel.org \
    --cc=treding@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox