On 03-08-18, 10:47, Peter Ujfalusi wrote: > > > On 2018-08-03 10:19, Huang Shijie wrote: > > Use dmaenginem_async_device_register to simplify the code: > > remove dma_async_device_unregister > > > > Signed-off-by: Huang Shijie <sjhu...@iluvatar.ai> > > --- > > drivers/dma/ti/omap-dma.c | 5 +---- > > 1 file changed, 1 insertion(+), 4 deletions(-) > > > > diff --git a/drivers/dma/ti/omap-dma.c b/drivers/dma/ti/omap-dma.c > > index a4a931ddf6f6..085748c6eb67 100644 > > --- a/drivers/dma/ti/omap-dma.c > > +++ b/drivers/dma/ti/omap-dma.c > > @@ -1566,7 +1566,7 @@ static int omap_dma_probe(struct platform_device > > *pdev) > > } > > } > > > > - rc = dma_async_device_register(&od->ddev); > > + rc = dmaenginem_async_device_register(&od->ddev); > > Why it is dmaenginem_async_device_register() and not aligned other > resource managed functions (devm_* dmam_*), like > devm_dma_async_device_register() > > and in dmaenginem_async_device_register() what is the 'm' in dmaenginem ? > DMAengine Managed?
yup, as you rightly said we could have done devm_dmaengine... or like few others do dmaenginem_ Yes it makes a little odd API but am trying to move away from dma_ to dmaengine_ for everything new.. -- ~Vinod
