[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7c946e2a-6fd4-f4c8-8afe-f9d0125fdaa0@nvidia.com>
Date: Tue, 30 Jun 2020 16:22:03 +0530
From: Vidya Sagar <vidyas@...dia.com>
To: Jon Hunter <jonathanh@...dia.com>, <bhelgaas@...gle.com>,
<lorenzo.pieralisi@....com>, <rjw@...ysocki.net>,
<lenb@...nel.org>, <andrew.murray@....com>, <treding@...dia.com>
CC: <linux-tegra@...r.kernel.org>, <linux-pci@...r.kernel.org>,
<linux-acpi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<kthota@...dia.com>, <mmaddireddy@...dia.com>, <sagar.tv@...il.com>
Subject: Re: [PATCH V3 1/2] arm64: tegra: Re-order PCIe aperture mappings to
support ACPI boot
On 29-Jun-20 7:01 PM, Jon Hunter wrote:
> Hi Sagar,
>
> On 10/01/2020 19:14, Vidya Sagar wrote:
>> Re-order Tegra194's PCIe aperture mappings to have IO window moved to
>> 64-bit aperture and have the entire 32-bit aperture used for accessing
>> the configuration space. This makes it to use the entire 32MB of the 32-bit
>> aperture for ECAM purpose while booting through ACPI.
>>
>> Signed-off-by: Vidya Sagar <vidyas@...dia.com>
>
> Any reason why we should not merge this change, even if patch 2/2 is not
> accepted? If there is no harm in us merging this, this would be one less
> change for us to carry out-of-tree. If so, can you update and re-post
> for 5.9?
There is no issue in merging this change alone. I'll send a patch for
review for 5.9 soon.
Thanks,
Vidya Sagar
>
> Cheers
> Jon
>
Powered by blists - more mailing lists