From: Vidya Sagar <vidyas-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Thierry Reding <treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org"
<bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
kthota-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
mmaddireddy-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH V2 0/7] Tegra PCIe end point config space map code refactoring
Date: Mon, 23 Oct 2017 20:54:53 +0530 [thread overview]
Message-ID: <fba4fe22-1401-1653-0985-e1ffafb29ded@nvidia.com> (raw)
In-Reply-To: <CAL_Jsq+3UAwk5gNgh=s6O1f-MadyGCtADX7pyzX8eUfBqboRfA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Monday 23 October 2017 08:40 PM, Rob Herring wrote:
> On Mon, Oct 23, 2017 at 9:35 AM, Vidya Sagar <vidyas-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org> wrote:
>> PCIe host controller in Tegra SoCs has 1GB of aperture available
>> for mapping end points config space, IO and BARs. In that, currently
>> 256MB is being reserved for mapping end points configuration space
>> which leaves less memory space available for mapping end points BARs
>> on some of the platforms.
>> This patch series attempts to use only 4K space from 1GB aperture to
>> access end points configuration space.
>>
>> Currently, this change benefits T20 and T186 in saving (i.e. repurposed
>> to use for BAR mapping) physical space as well as kernel virtual mapping space,
>> it saves only kernel virtual address space in T30, T124, T132 and T210.
>>
>> NOTE: Both driver and DT changes are inter-dependent and hence need to go together
> You are breaking compatibility with any other OS.
>
> Can't this easily be solved within the kernel by adjusting the
> resource size? To save the virtual space, you only need patch 1 and
> don't need the DT change. The DT change is just for phys address space
> for BARs.
In case of T20 & T186, DT change is required to re-purpose address space
which otherwise
is used for config space mapping to map BARs. In case of other chips, DT
changes
are also required because the 4K being used for mapping config space is
taken from the
last 4K chunk of 256MB instead of first 4K chunk to align with driver
change.
>> Testing Done on T124, T210 & T186:
>> Enumeration and basic functionality of immediate devices
>> Enumeration of devices behind a PCIe switch
>> Complete 4K configuration space access
>>
>> Vidya Sagar (7):
>> PCI: tegra: refactor config space mapping code
>> ARM: tegra: limit PCIe config space mapping to 4K for T20
>> ARM: tegra: limit PCIe config space mapping to 4K for T30
>> ARM: tegra: limit PCIe config space mapping to 4K for T124
>> ARM64: tegra: limit PCIe config space mapping to 4K for T132
>> ARM64: tegra: limit PCIe config space mapping to 4K for T210
>> ARM64: tegra: limit PCIe config space mapping to 4K for T186
>>
>> arch/arm/boot/dts/tegra124.dtsi | 2 +-
>> arch/arm/boot/dts/tegra20.dtsi | 8 +--
>> arch/arm/boot/dts/tegra30.dtsi | 2 +-
>> arch/arm64/boot/dts/nvidia/tegra132.dtsi | 2 +-
>> arch/arm64/boot/dts/nvidia/tegra186.dtsi | 8 +--
>> arch/arm64/boot/dts/nvidia/tegra210.dtsi | 2 +-
>> drivers/pci/host/pci-tegra.c | 109 +++++++++----------------------
>> 7 files changed, 42 insertions(+), 91 deletions(-)
>>
>> --
>> 2.7.4
>>
next prev parent reply other threads:[~2017-10-23 15:24 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 [this message]
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 ` [PATCH V2 7/7] ARM64: tegra: limit PCIe config space mapping to 4K for T186 Vidya Sagar
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=fba4fe22-1401-1653-0985-e1ffafb29ded@nvidia.com \
--to=vidyas-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kthota-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mmaddireddy-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=treding-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
/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