[PATCH V5 05/12] drivers: platform: Configure dma operations at probe time
sricharan at codeaurora.org
Thu Jan 19 21:34:19 PST 2017
>From: Lorenzo Pieralisi [mailto:lorenzo.pieralisi at arm.com]
>Sent: Thursday, January 19, 2017 10:18 PM
>To: Sricharan R <sricharan at codeaurora.org>
>Cc: robin.murphy at arm.com; will.deacon at arm.com; joro at 8bytes.org; iommu at lists.linux-foundation.org; linux-arm-
>kernel at lists.infradead.org; linux-arm-msm at vger.kernel.org; m.szyprowski at samsung.com
>Subject: Re: [PATCH V5 05/12] drivers: platform: Configure dma operations at probe time
>On Thu, Jan 19, 2017 at 08:35:49PM +0530, Sricharan R wrote:
>> Configuring DMA ops at probe time will allow deferring device probe when
>> the IOMMU isn't available yet. The dma_configure for the device is
>> now called from the generic device_attach callback just before the
>> bus/driver probe is called. This way, configuring the DMA ops for the
>> device would be called at the same place for all bus_types, hence the
>> deferred probing mechanism should work for all buses as well.
>> 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
>> Similarly on the device/driver_unregister path __device_release_driver is
>> called which inturn calls dma_deconfigure.
>> Signed-off-by: Sricharan R <sricharan at codeaurora.org>
>> * Removed the dma configuration for the pci devices in case of DT
>> from pci_dma_configure which was hanging outside separately and
>> doing it in dma_configure function itself.
>Rename the patch subject then, it is misleading.
Ha, infact the patch still does what it says. The above words were
to mention what was changed from V4 to V5. Sorry i should have
mentioned that explicitly.
More information about the linux-arm-kernel