The common code aready has the flow:
really_probe->dma_configure->of_dma_configure
There is no need to call it in driver specific probe function.
With of_dma_configure call twice, arch_setup_dma_ops will set
dev->dma_ops and dev->archdata.dev_dma_ops both to xen_dma_ops
when booting Kernel in Dom0 and cause stack overflow in
dma_alloc_coherent.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
Acked-by: Fugang Duan <fugang.duan@nxp.com>
71116925ee