Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754063AbbLOPVF (ORCPT ); Tue, 15 Dec 2015 10:21:05 -0500 Received: from comal.ext.ti.com ([198.47.26.152]:45823 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753854AbbLOPVE (ORCPT ); Tue, 15 Dec 2015 10:21:04 -0500 Subject: Re: [PATCH 2/6] ARM: DTS: da850: Use the new DT bindings for the eDMA3 To: Peter Ujfalusi References: <1449237210-16381-1-git-send-email-peter.ujfalusi@ti.com> <1449237210-16381-3-git-send-email-peter.ujfalusi@ti.com> <566FDF93.7050005@ti.com> <566FFD1C.4080000@ti.com> <56701A47.9090105@ti.com> <56701E2C.7060308@ti.com> CC: , , , From: Sekhar Nori Message-ID: <56702FC3.5050705@ti.com> Date: Tue, 15 Dec 2015 20:50:35 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <56701E2C.7060308@ti.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1666 Lines: 35 On Tuesday 15 December 2015 07:35 PM, Peter Ujfalusi wrote: > On 12/15/2015 03:48 PM, Sekhar Nori wrote: >>>> In future, if/when we gain QDMA support, the QDMA channels could be used >>>> for memcopy. >>> >>> Well, in short there is no way to get the qDMA working in a different way >>> either. qDMA channel is in essence using 'normal' eDMA channel. This means >>> that we still need to reserve the eDMA channel to be used for memcpy, but >>> instead of SW triggering it (as we do it right now), we would need to use the >>> channel as qDMA and set things up accordingly. I don't really see the benefit >>> for qDMA mode to be honest. >> >> I guess the only advantage is that they will not clash with peripheral >> mode usage. But even then, some sort of reservation is needed. So I >> guess QDMA is no better than the EDMA reserved channels? > > It will clash with the peripheral mode use since it needs to take one of the > eDMA channels. qDMA mode is basically differs from the mode we are using by > how the channel is triggered. Currently we start the memcpy with SW trigger. Alright, so I was missing this detail. Thanks for clarifying it on IRC. The EDMA specification makes it look like 8 additional QDMA channels can be used over 32 DMA channels, but in reality they are not additional channels since TCC is only valid between 0-31. So, I agree. QDMA does not buy us any parallel transfers. Thanks, Sekhar -- 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/