From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [PATCH v3 2/3] ACPI / OSL: Allow PCI to be disabled Date: Tue, 11 Dec 2018 22:46:34 +0100 Message-ID: References: <20181210181315.5023-1-okaya@kernel.org> <20181210181315.5023-2-okaya@kernel.org> <20181211170957.GA335@infradead.org> <342c5dd9-cb3d-d714-c87f-814a942cf395@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <342c5dd9-cb3d-d714-c87f-814a942cf395@kernel.org> Sender: linux-kernel-owner@vger.kernel.org To: okaya@kernel.org Cc: Christoph Hellwig , ACPI Devel Maling List , "Rafael J. Wysocki" , Len Brown , Linux Kernel Mailing List List-Id: linux-acpi@vger.kernel.org On Tue, Dec 11, 2018 at 6:37 PM Sinan Kaya wrote: > > On 12/11/2018 12:09 PM, Christoph Hellwig wrote: > > On Mon, Dec 10, 2018 at 06:13:14PM +0000, Sinan Kaya wrote: > >> Getting ready to allow PCI to be disabled with ACPI enabled. Stub > >> out calls that depend on PCI. > > > > I think you want to skip building at least all of hwpci.c if CONFIG_PCI > > is disabled. Or replace that whole stiking pile of crap with something > > resembling C code.. > > > > I can give it a try but I'm under the impression that we don't touch > ACPICA code in general. > > Feel free to correct me. We don't as a rule, but depending on what the patch looks like, we might not follow the rule this time. I wonder though what we do if some AML wants to access PCI config space via an opregion in there. Have you thought about that?