Re: [PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely dt property

2016-04-11 Thread gpramod
On 2016-04-06 04:26, Stanimir Varbanov wrote: Some of the peripherals has bam which is controlled by remote processor, thus the bam dma driver must avoid register writes which initialise bam hw block. Those registers are protected from xPU block and any writes to them will lead to secure

Re: [PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely dt property

2016-04-11 Thread gpramod
On 2016-04-06 04:26, Stanimir Varbanov wrote: Some of the peripherals has bam which is controlled by remote processor, thus the bam dma driver must avoid register writes which initialise bam hw block. Those registers are protected from xPU block and any writes to them will lead to secure

Re: [PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely dt property

2016-04-07 Thread Rob Herring
On Wed, Apr 06, 2016 at 01:56:20AM +0300, Stanimir Varbanov wrote: > Some of the peripherals has bam which is controlled by remote > processor, thus the bam dma driver must avoid register writes > which initialise bam hw block. Those registers are protected > from xPU block and any writes to them

Re: [PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely dt property

2016-04-07 Thread Rob Herring
On Wed, Apr 06, 2016 at 01:56:20AM +0300, Stanimir Varbanov wrote: > Some of the peripherals has bam which is controlled by remote > processor, thus the bam dma driver must avoid register writes > which initialise bam hw block. Those registers are protected > from xPU block and any writes to them

Re: [PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely dt property

2016-04-06 Thread Stanimir Varbanov
On 04/06/2016 02:44 AM, Vinod Koul wrote: > On Wed, Apr 06, 2016 at 01:56:20AM +0300, Stanimir Varbanov wrote: >> Documentation/devicetree/bindings/dma/qcom_bam_dma.txt | 2 ++ >> drivers/dma/qcom/bam_dma.c | 7 +++ > > The binding should be a separate patch.. I'm

Re: [PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely dt property

2016-04-06 Thread Stanimir Varbanov
On 04/06/2016 02:44 AM, Vinod Koul wrote: > On Wed, Apr 06, 2016 at 01:56:20AM +0300, Stanimir Varbanov wrote: >> Documentation/devicetree/bindings/dma/qcom_bam_dma.txt | 2 ++ >> drivers/dma/qcom/bam_dma.c | 7 +++ > > The binding should be a separate patch.. I'm

Re: [PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely dt property

2016-04-06 Thread Andy Gross
On Tue, Apr 05, 2016 at 04:44:25PM -0700, Vinod Koul wrote: > On Wed, Apr 06, 2016 at 01:56:20AM +0300, Stanimir Varbanov wrote: > > Documentation/devicetree/bindings/dma/qcom_bam_dma.txt | 2 ++ > > drivers/dma/qcom/bam_dma.c | 7 +++ > > The binding should be a

Re: [PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely dt property

2016-04-06 Thread Andy Gross
On Tue, Apr 05, 2016 at 04:44:25PM -0700, Vinod Koul wrote: > On Wed, Apr 06, 2016 at 01:56:20AM +0300, Stanimir Varbanov wrote: > > Documentation/devicetree/bindings/dma/qcom_bam_dma.txt | 2 ++ > > drivers/dma/qcom/bam_dma.c | 7 +++ > > The binding should be a

Re: [PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely dt property

2016-04-05 Thread Vinod Koul
On Wed, Apr 06, 2016 at 01:56:20AM +0300, Stanimir Varbanov wrote: > Documentation/devicetree/bindings/dma/qcom_bam_dma.txt | 2 ++ > drivers/dma/qcom/bam_dma.c | 7 +++ The binding should be a separate patch.. > > + bdev->controlled_remotely =

Re: [PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely dt property

2016-04-05 Thread Vinod Koul
On Wed, Apr 06, 2016 at 01:56:20AM +0300, Stanimir Varbanov wrote: > Documentation/devicetree/bindings/dma/qcom_bam_dma.txt | 2 ++ > drivers/dma/qcom/bam_dma.c | 7 +++ The binding should be a separate patch.. > > + bdev->controlled_remotely =

[PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely dt property

2016-04-05 Thread Stanimir Varbanov
Some of the peripherals has bam which is controlled by remote processor, thus the bam dma driver must avoid register writes which initialise bam hw block. Those registers are protected from xPU block and any writes to them will lead to secure violation and system reboot. Adding the

[PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely dt property

2016-04-05 Thread Stanimir Varbanov
Some of the peripherals has bam which is controlled by remote processor, thus the bam dma driver must avoid register writes which initialise bam hw block. Those registers are protected from xPU block and any writes to them will lead to secure violation and system reboot. Adding the