quoted

Yes agreed on that, plus the runtime handling needs to be built in, right
now the APIs dont work well with it, we disucssed these during the KS and
this goes without saying, patches are welcome :)

Okay, so what is the conclusion? Do you want me to do the whole rework of
dma
engine core to get this runtime pm patchset for pl330 merged??? Is there any
roadmap for this rework prepared, so I can at least take a look at the
amount
of work needed to be done?

I'm rather new to dma engine framework and I only wanted to fix pl330 driver
not to block turning off the power domain on Exynos5422/5433 SoCs.

As you probably know, this is a common problem for many dma devices,
slave devices and platforms.

If possible, it would be great if we could avoid a solution that
doesn't force changes to lots of "dma consumer" drivers.

I can also check again if there is any other way to find the slave device in
alloc_chan_resources, like for example scanning the device tree for
phandles,
to avoid changing dmaengine core as this turned out to be too problematic
before one will do the proper dma engine core rework.

Again, thanks for working on this!

Kind regards
Uffe