Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751614AbaFZUa2 (ORCPT ); Thu, 26 Jun 2014 16:30:28 -0400 Received: from smtp.codeaurora.org ([198.145.11.231]:58832 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750974AbaFZUa0 (ORCPT ); Thu, 26 Jun 2014 16:30:26 -0400 From: Andy Gross To: Vinod Koul Cc: Bjorn Andersson , Dan Williams , dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, Kumar Gala , devicetree@vger.kernel.org, Andy Gross Subject: [PATCH 0/2] Add Qualcomm ADM dmaengine driver Date: Thu, 26 Jun 2014 15:30:14 -0500 Message-Id: <1403814616-23917-1-git-send-email-agross@codeaurora.org> X-Mailer: git-send-email 1.7.9.5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This patch set introduces the dmaengine driver for the Qualcomm Application Data Mover (ADM) DMA controller present on MSM8960, APQ8064, and IPQ8064 devices. The initial version of this driver will only support slave DMA operations between system memory and peripherals. Flow control via the CRCI (client rate control interface) is supported and can be configured via device tree configuration. Flow control usage is required for some peripheral devices. Andy Gross (2): dmaengine: Add QCOM ADM DMA driver dmaengine: qcom_adm: Add device tree binding Documentation/devicetree/bindings/dma/qcom_adm.txt | 60 ++ drivers/dma/Kconfig | 10 + drivers/dma/Makefile | 1 + drivers/dma/qcom_adm.c | 872 ++++++++++++++++++++ 4 files changed, 943 insertions(+) create mode 100644 Documentation/devicetree/bindings/dma/qcom_adm.txt create mode 100644 drivers/dma/qcom_adm.c -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/