On Tuesday 30 September 2014 18:48:21 Liviu Dudau wrote: > > > > > These are the functions I found that refer to pci_sys_data on arm32: > > > > > > > > > > pcibios_add_bus > > > > > pcibios_remove_bus > > These are only needed if you want to do per HB processing of the bus > > > > > > pcibios_align_resource > > mvebu is the only user of this function. > > > > > > pci_mmap_page_range > > This is only needed when mapping a PCI resource to userspace. Is that your case here? > > > > > > pci_domain_nr > > > > > pci_proc_domain > > We have equivalent functionality in the generic patches for those. > We clearly don't need those functions for the new drivers, but that's not the point. The problem is that when you build a kernel that has both a traditional host bridge driver and a new one in it, you always get those functions and they get called from the PCI core, with incorrect arguments. Arnd -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
