Hi Hanjun, >On 2017/1/24 0:18, Sricharan R wrote: >> This series calls the dma ops configuration for the devices >> at a generic place so that it works for all busses. >> The dma_configure_ops for a device is now called during >> the device_attach callback just before the probe of the >> bus/driver is called. Similarly dma_deconfigure is called during >> device/driver_detach path. >> >> pci_bus_add_devices (platform/amba)(_device_create/driver_register) >> | | >> pci_bus_add_device (device_add/driver_register) >> | | >> device_attach device_initial_probe >> | | >> __device_attach_driver __device_attach_driver >> | >> driver_probe_device >> | >> really_probe >> | >> dma_configure >> >> Similarly on the device/driver_unregister path __device_release_driver is >> called which inturn calls dma_deconfigure. >> >> Took the reworked patches [2] from Robin's branch and >> rebased on top of Lorenzo's ACPI IORT ARM support series [3]. >> >> * Tested with platform and pci devices for probe deferral >> and reprobe on arm64 based platform. >> * Need help for testing with ACPI. > >Cherry picked this patch set with no conflict with my platform >msi patches, and test it on Hisilicon D03 (ARM64 platform with >SMMUv3) with ACPI, it boots ok as before and the native NIC and >SAS (platform devices) are working properly. > >for ACPI and the core code changes: > >Tested-by: Hanjun Guo <hanjun.guo@xxxxxxxxxx> Thanks for the testing with ACPI + SMMUV3 Regards, Sricharan -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
