From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753920AbcL3Lcs (ORCPT ); Fri, 30 Dec 2016 06:32:48 -0500 Received: from smtprelay.synopsys.com ([198.182.60.111]:45268 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753851AbcL3Lco (ORCPT ); Fri, 30 Dec 2016 06:32:44 -0500 To: "dmaengine@vger.kernel.org" , "linux-kernel@vger.kernel.org" From: Jose Abreu Subject: dmaengine: dw-dmac: Custom cyclic API (Why?) Message-ID: Date: Fri, 30 Dec 2016 11:32:39 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.107.19.26] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi All, I am going to work with dw-dmac AHB controller and I wanted to use SND_DMAENGINE_PCM. In order to use this, a standard DMA driver with cyclic support is needed. I found out that dw-dmac is capable of cyclic transfers but instead of using the DMA engine standard cyclic API it uses a custom API. Is there any specific reason for this? What is the effort to change the custom API to a standard DMA engine cyclic API? Best regards, Jose Miguel Abreu