On Thu, Dec 5, 2013 at 4:04 PM, Arnd Bergmann <a...@arndb.de> wrote: > On Wednesday 04 December 2013, Hanjun Guo wrote: >> On 2013年12月04日 00:41, Matthew Garrett wrote: >> > Given the number of #ifdefs you're adding, wouldn't it make more sense >> > to just add stub functions to include/linux/pci.h? >> >> Thanks for the suggestion :) >> >> I can add stub functions in include/linux/pci.h for raw_pci_read()/ >> raw_pci_write(), then can remove #ifdefs for >> acpi_os_read/write_pci_configuration(). > > Actually I wonder about the usefulness of this patch in either form: Since > ACPI > on ARM64 is only for servers, I would very much expect them to always come > with > PCI, either physical host bridges with attached devices, or logical PCI > functions > used to describe the on-SoC I/O devices. Even in case of virtual machines, > you'd > normally use PCI as the method to communicate data about the virtio channels. > > Can you name a realistic use-case where you'd want ACPI but not PCI?
Calxeda h/w. Yes, we do have PCI, but it is optional. Rob -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
