Re: [PATCH] dmaengine: qcom_bam_dma: add one more optional clock

Hi Andy, On 09/07/2014 08:55 PM, Stanimir Varbanov wrote: > The BAM is tightly coupled with the peripheral to which it > belongs. In that sprit to access the BAM configuration > registers the driver needs to enable some peripheral > clocks. Currently the DT node enables bamclk which seems > is not

Re: [PATCH] dmaengine: qcom_bam_dma: add one more optional clock

Hi Mark, Thank you for the comments! On 09/08/2014 01:36 PM, Mark Rutland wrote: > On Sun, Sep 07, 2014 at 06:55:47PM +0100, Stanimir Varbanov wrote: >> The BAM is tightly coupled with the peripheral to which it >> belongs. In that sprit to access the BAM configuration >> registers the driver nee

Re: [PATCH] dmaengine: qcom_bam_dma: add one more optional clock

On Sun, Sep 07, 2014 at 06:55:47PM +0100, Stanimir Varbanov wrote: > The BAM is tightly coupled with the peripheral to which it > belongs. In that sprit to access the BAM configuration > registers the driver needs to enable some peripheral > clocks. Currently the DT node enables bamclk which seems

[PATCH] dmaengine: qcom_bam_dma: add one more optional clock

The BAM is tightly coupled with the peripheral to which it belongs. In that sprit to access the BAM configuration registers the driver needs to enable some peripheral clocks. Currently the DT node enables bamclk which seems is not enough for some peripherals (for example the crypto engine wants cor