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>, Vidya Sagar <vidyas@nvidia.com>
Subject: [PATCH 6/6] ARM64: tegra: limit PCIe config space mapping to 4K for T210
Date: Fri, 13 Oct 2017 00:20:11 +0530 [thread overview]
Message-ID: <1507834211-24922-7-git-send-email-vidyas@nvidia.com> (raw)
In-Reply-To: <1507834211-24922-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/tegra210.dtsi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/boot/dts/nvidia/tegra210.dtsi b/arch/arm64/boot/dts/nvidia/tegra210.dtsi
index 29f471e0f22a..8cad2516597b 100644
--- a/arch/arm64/boot/dts/nvidia/tegra210.dtsi
+++ b/arch/arm64/boot/dts/nvidia/tegra210.dtsi
@@ -16,7 +16,7 @@
device_type = "pci";
reg = <0x0 0x01003000 0x0 0x00000800 /* PADS registers */
0x0 0x01003800 0x0 0x00000800 /* AFI registers */
- 0x0 0x02000000 0x0 0x10000000>; /* configuration space */
+ 0x0 0x11FFF000 0x0 0x00001000>; /* configuration space */
reg-names = "pads", "afi", "cs";
interrupts = <GIC_SPI 98 IRQ_TYPE_LEVEL_HIGH>, /* controller interrupt */
<GIC_SPI 99 IRQ_TYPE_LEVEL_HIGH>; /* MSI interrupt */
--
2.7.4
next prev parent reply other threads:[~2017-10-12 18:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 18:50 [PATCH 0/6] Tegra PCIe end point config space map code refactoring Vidya Sagar
2017-10-12 18:50 ` [PATCH 1/6] PCI: tegra: refactor config space mapping code Vidya Sagar
2017-10-20 19:08 ` Bjorn Helgaas
2017-10-23 5:39 ` Vidya Sagar
2017-10-23 13:33 ` Bjorn Helgaas
2017-10-12 18:50 ` [PATCH 2/6] ARM: tegra: limit PCIe config space mapping to 4K for T20 Vidya Sagar
2017-10-12 18:50 ` [PATCH 3/6] ARM: tegra: limit PCIe config space mapping to 4K for T30 Vidya Sagar
2017-10-12 18:50 ` [PATCH 4/6] ARM: tegra: limit PCIe config space mapping to 4K for T124 Vidya Sagar
2017-10-12 18:50 ` [PATCH 5/6] ARM64: tegra: limit PCIe config space mapping to 4K for T132 Vidya Sagar
2017-10-12 18:50 ` Vidya Sagar [this message]
2017-10-15 6:21 ` [PATCH 0/6] Tegra PCIe end point config space map code refactoring Manikanta Maddireddy
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=1507834211-24922-7-git-send-email-vidyas@nvidia.com \
--to=vidyas@nvidia.com \
--cc=bhelgaas@google.com \
--cc=kthota@nvidia.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.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;
as well as URLs for NNTP newsgroup(s).