From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752013AbcLFUaF (ORCPT ); Tue, 6 Dec 2016 15:30:05 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48328 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751254AbcLFUaD (ORCPT ); Tue, 6 Dec 2016 15:30:03 -0500 Subject: Re: [PATCH v3] PCI/ACPI: xgene: Add ECAM quirk for X-Gene PCIe controller To: Bjorn Helgaas References: <1480620053.4751.30.camel@redhat.com> <20161201194114.GA8263@bhelgaas-glaptop.roam.corp.google.com> <20161201230736.GA17948@bhelgaas-glaptop.roam.corp.google.com> <20161202233943.GF9903@bhelgaas-glaptop.roam.corp.google.com> <62dd5462-4d68-b89f-2b45-0d58bbd96bcd@redhat.com> <20161205212140.GA18259@bhelgaas-glaptop.roam.corp.google.com> <20161206201835.GA19700@bhelgaas-glaptop.roam.corp.google.com> Cc: Duc Dang , Mark Salter , Rafael Wysocki , Lorenzo Pieralisi , Arnd Bergmann , linux-pci@vger.kernel.org, linux-arm , Linux Kernel Mailing List , Tomasz Nowicki , patches From: Jon Masters Message-ID: <0a96dada-59de-157f-cbfd-daca229a736a@redhat.com> Date: Tue, 6 Dec 2016 15:23:34 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <20161206201835.GA19700@bhelgaas-glaptop.roam.corp.google.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Tue, 06 Dec 2016 20:23:39 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/06/2016 03:18 PM, Bjorn Helgaas wrote: > On Tue, Dec 06, 2016 at 02:46:00PM -0500, Jon Masters wrote: >> On 12/05/2016 04:21 PM, Bjorn Helgaas wrote: >>> On Fri, Dec 02, 2016 at 07:33:46PM -0500, Jon Masters wrote: >> >>>>> Even without this patch, I don't think it's a show-stopper to have >>>>> Linux mistakenly thinking this region is routed to PCI, because the >>>>> driver does reserve it and the PCI core will never try to use it. >>>> >>>> Ok. So are you happy with pulling in Duc's v4 patch and retaining >>>> status quo on the bridge resources for 4.10? >>> >>> Yes, I think it looks good. I'll finish packaging things up and >>> repost the current series. >> >> Ok, great. So you're still pretty confident we'll have "out of the box" >> booting on these machines for 4.10? :) > > I just merged pci/ecam into my "next" branch, so as long as tomorrow's > linux-next boots out of the box, we should be set. I made the following > changes compared to v11: > > - dropped the x86 change to use acpi_resource_consumer() > - added parens around macro args used in arithmetic expressions > - renamed "seg" to "node" in THUNDER_PEM_RES and THUNDER_PEM_QUIRK > - incorporated (u64) cast and dropped "UL" postfix for THUNDER_PEM_QUIRK > > Let me know if you see any issues. Thanks - I'll test linux-next tomorrow. Jon. -- Computer Architect | Sent from my Fedora powered laptop