On Tue, Oct 4, 2016 at 9:04 PM, Vinod Koul <vinod.koul@xxxxxxxxx> wrote: > On Mon, Oct 03, 2016 at 01:19:37PM +0530, Muni Sekhar wrote: >> Hi All, >> >> I see that following dma engine driver uses MODULE_DEVICE_TABLE with ‘type=of’. >> What does ‘type=of’ mean? How to trigger this driver’s probe and >> remove to be called? > > it means open firmware. This is specfied here by Device tree, so if you have this > device you need to have the bindings as well. I don’t have that device, but I have PLDA’s EZDMA DMA engine on PCIe interface. It contains two channels, one is to transmit to the device and another is to receive from the device. I checked Linux kernel tree but could not find the pre-existing driver, but I see different DMA engine drivers. So I thought of playing with the existing closer DMA engine driver. > > see Documentation/devicetree/bindings/dma/xilinx/zynqmp_dma.txt > >> >> >> >> http://lxr.linux.no/linux+v4.8/drivers/dma/xilinx/zynqmp_dma.c >> >> >> >> static const struct of_device_id zynqmp_dma_of_match[] = { >> >> { .compatible = "xlnx,zynqmp-dma-1.0", }, >> >> {} >> >> }; >> >> MODULE_DEVICE_TABLE(of, zynqmp_dma_of_match); >> >> >> >> static struct platform_driver zynqmp_dma_driver = { >> >> .driver = { >> >> .name = "xilinx-zynqmp-dma", >> >> .of_match_table = zynqmp_dma_of_match, >> >> }, >> >> .probe = zynqmp_dma_probe, >> >> .remove = zynqmp_dma_remove, >> >> }; >> >> >> >> module_platform_driver(zynqmp_dma_driver); >> >> >> >> MODULE_AUTHOR("Xilinx, Inc."); >> >> MODULE_DESCRIPTION("Xilinx ZynqMP DMA driver"); >> >> >> -- >> Thanks, >> Sekhar >> -- >> To unsubscribe from this list: send the line "unsubscribe dmaengine" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- > ~Vinod -- Thanks, Sekhar -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
