[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160407175752.GM32257@rob-hp-laptop>
Date: Thu, 7 Apr 2016 12:57:52 -0500
From: Rob Herring <robh@...nel.org>
To: Stanimir Varbanov <stanimir.varbanov@...aro.org>
Cc: Mark Rutland <mark.rutland@....com>,
Vinod Koul <vinod.koul@...el.com>,
Andy Gross <andy.gross@...aro.org>,
linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org,
dmaengine@...r.kernel.org, Sinan Kaya <okaya@...eaurora.org>,
Pramod Gurav <gpramod@...eaurora.org>
Subject: Re: [PATCH v2 3/5] dmaengine: qcom: bam_dma: add controlled remotely
dt property
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 will lead to secure
> violation and system reboot.
>
> Adding the contolled_remotely flag in bam driver to avoid
> not permitted register writes in bam_init function.
>
> Signed-off-by: Stanimir Varbanov <stanimir.varbanov@...aro.org>
> Reviewed-by: Andy Gross <andy.gross@...aro.org>
> ---
> Documentation/devicetree/bindings/dma/qcom_bam_dma.txt | 2 ++
> drivers/dma/qcom/bam_dma.c | 7 +++++++
> 2 files changed, 9 insertions(+)
Acked-by: Rob Herring <robh@...nel.org>
On being a separate patch, yes that is always the preference. However,
this change is so small it doesn't matter to me. But this is going in
thru Vinod's tree, so it is his call.
Rob
Powered by blists - more mailing lists