[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <319ca097-4b10-83b9-841c-52adccbb48ad@nvidia.com>
Date: Tue, 6 Sep 2016 12:33:45 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Nicolin Chen <nicoleotsuka@...il.com>, <vinod.koul@...el.com>
CC: <linux-kernel@...r.kernel.org>, <linux-tegra@...r.kernel.org>,
<dmaengine@...r.kernel.org>, <gnurou@...il.com>,
<thierry.reding@...il.com>, <swarren@...dotorg.org>,
<ldewangan@...dia.com>
Subject: Re: [PATCH v2 0/2] Add memcpy support for tegra210-adma
On 03/09/16 01:32, Nicolin Chen wrote:
> This series of patches add memcpy support for tegra210 ADMA engine.
Thanks. Any reason you choose this DMA and not the APB DMA? The APB DMA
is more of a generic DMA and so for memcpy it would seem to be a good
choice and it is available on all Tegras not just Tegra210.
Furthermore, from a power standpoint the ADMA is in the audio power
domain and so using it for memcpy would mean the audio power domain is
turned on. It may not be a big deal for some, but given the APB is in
the CORE domain (always on when not in low-power) it seems like a better
choice for power as well.
Cheers
Jon
--
nvpublic
Powered by blists - more mailing lists