linux-toradex.git/drivers/dma/qcom, branch v4.17

dmaengine: qcom: bam_dma: check if the runtime pm enabled

2018-05-17T10:46:49+00:00

Disabling pm runtime at probe is not sufficient to get BAM working
on remotely controller instances. pm_runtime_get_sync() would return
-EACCES in such cases.
So check if runtime pm is enabled before returning error from bam functions.

Fixes: 5b4a68952a89 ("dmaengine: qcom: bam_dma: disable runtime pm on remote controlled")
Signed-off-by: Srinivas Kandagatla 
Signed-off-by: Vinod Koul

dmaengine: qcom: bam_dma: disable runtime pm on remote controlled

2018-03-01T08:44:27+00:00

Remotely controlled BAM instance should not do any power management from
CPU side, as cpu can not reliably say if the BAM is busy or not.

Disable it for such instances.

Signed-off-by: Srinivas Kandagatla 
Signed-off-by: Vinod Koul

dmaengine: qcom: bam_dma: do not write to global regs in remote mode

2018-03-01T08:44:27+00:00

BAM_DESC_CNT_TRSHLD register is global register, which can only be written
when BAM is in master mode, So check the mode of operation before writing
it.

Without this check SOC's xPU would catch such access and crash the system.
First noticed on DB820c while testing SLIMBus BAM.

Signed-off-by: Srinivas Kandagatla 
Signed-off-by: Vinod Koul

dmaengine: qcom: bam_dma: get num-channels and num-ees from dt

2018-03-01T08:44:27+00:00

When Linux is master of BAM, it can directly read registers to know number
of supported channels, however when its remotely controlled reading these
registers would trigger a crash if the BAM is not yet initialized or
powered up on the remote side.

This patch allows driver to read num-channels and num-ees from Device Tree
for remotely controlled BAM.

Signed-off-by: Srinivas Kandagatla 
Signed-off-by: Vinod Koul

dmaengine: qcom: bam_dma: make bam clk optional

2018-03-01T08:44:27+00:00

When BAM is remotely controlled it does not sound correct to control
its clk on Linux side. Make it optional, so that its not mandatory
for remote controlled BAM instances.

Signed-off-by: Srinivas Kandagatla 
Signed-off-by: Vinod Koul

Merge branch 'topic/qcom_hidma' into for-linus

2018-01-31T08:20:40+00:00

dmaengine: qcom_hidma: simplify DT resource parsing

2018-01-08T17:01:02+00:00

The hidma driver open codes populating address and IRQ resources from DT.
We have standard functions of_address_to_resource and of_irq_to_resource
for this, so use them instead.

The DT binding states each child should have 2 addresses and 1 IRQ, so we
can simplify the logic and do a fixed size resource allocation. Using the
standard of_address_to_resource will also do any address translation which
was missing.

Signed-off-by: Rob Herring 
Reviewed-by: Sinan Kaya 
Signed-off-by: Vinod Koul

dmaengine: qcom_hidma: Add identity register support

2017-12-13T08:42:10+00:00

The location for destination event channel register has been relocated from
offset 0x28 to 0x40. Update the code accordingly.

Signed-off-by: Sinan Kaya 
Signed-off-by: Vinod Koul

dmaengine: qcom_hidma: Add support for the new revision

2017-12-13T08:42:10+00:00

Add support for probing the newer HW and also organize MSI capable hardware
into an array for maintenance reasons.

Signed-off-by: Sinan Kaya 
Signed-off-by: Vinod Koul

dmaengine: qcom_hidma: check pending interrupts

2017-12-12T05:32:43+00:00

Driver is missing the interrupts if two requests are queued up at the same
time as the interrupt handler is servicing a request that was just
delivered.

The ISR clears the interrupt at the end but it could be clearing the
interrupt for an outstanding event. Therefore, second interrupt never
arrives.

Clear the interrupt first and then check for completions.

Also, make sure that request start and interrupt clear do not overlap in
time by using a spinlock.

Signed-off-by: Sinan Kaya 
Signed-off-by: Vinod Koul