linux-kernel - [PATCH 0/2] Bypass BAM init if Remotely controlled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1458640151-15150-1-git-send-email-gpramod@codeaurora.org>
Date:	Tue, 22 Mar 2016 15:19:09 +0530
From:	Pramod Gurav <gpramod@...eaurora.org>
To:	andy.gross@...aro.org, linux-kernel@...r.kernel.org
Cc:	dmaengine@...r.kernel.org, linux-arm-msm@...r.kernel.org,
	devicetree@...r.kernel.org, dan.j.williams@...el.com,
	vinod.koul@...el.com, okaya@...eaurora.org, architt@...eaurora.org,
	Pramod Gurav <gpramod@...eaurora.org>
Subject: [PATCH 0/2] Bypass BAM init if Remotely controlled

On some QOCM platforms(eg 8996) BAM control registers are managed remotely
hence can not be accessed by application processor for writes. So skip the bam_init
for any such platform if DT property is set.

Tested on 8996 (BAM Global control is through remote) and DB410C boards.
Tested with i2c DMA on these targets which uses BAM as DMA controller.

Pramod Gurav (2):
  dmaengine: qcom_bam_dma: Clear IRQ only if its set
  dmaengine: qcom_bam_dma: Bypass BAM init if not managed locally

 .../devicetree/bindings/dma/qcom_bam_dma.txt        |  3 +++
 drivers/dma/qcom/bam_dma.c                          | 21 +++++++++++++--------
 2 files changed, 16 insertions(+), 8 deletions(-)

-- 
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation