From: Jon Hunter <jonathanh@nvidia.com>
To: Dmitry Osipenko <digetx@gmail.com>,
Nicolin Chen <nicoleotsuka@gmail.com>, <vinod.koul@intel.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<dmaengine@vger.kernel.org>, <gnurou@gmail.com>,
<thierry.reding@gmail.com>, <swarren@wwwdotorg.org>,
<ldewangan@nvidia.com>
Subject: Re: [PATCH v2 0/2] Add memcpy support for tegra210-adma
Date: Tue, 6 Sep 2016 14:04:20 +0100 [thread overview]
Message-ID: <6f45ff6e-5fa7-7aca-154c-85cf235aa62f@nvidia.com> (raw)
In-Reply-To: <5db4d7db-b1f4-c6af-de56-e8bb13ebc465@gmail.com>
On 06/09/16 13:03, Dmitry Osipenko wrote:
> On 06.09.2016 14:33, Jon Hunter wrote:
>>
>> 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.
>>
>
> Just a small clarification:
>
> If I'm not mistaken, APB DMA is mem-to-device, while AHB DMA is mem-to-mem. So,
> you probably meant AHB and not the APB.
Description from the Tegra TRM:
"The APB DMA Controller is placed between the AHB Bus and the APB Bus
and is a master on both buses.
The APB DMA Controller is used for block data transfers from a source
location to the destination location. The source may be
DRAM or IRAM, and the destination location could be devices placed on
APB Bus; or vice versa."
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2016-09-06 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 0:32 [PATCH v2 0/2] Add memcpy support for tegra210-adma Nicolin Chen
2016-09-03 0:32 ` [PATCH v2 1/2] dmaengine: tegra210-adma: Add pre-check for cyclic callback Nicolin Chen
2016-09-03 0:32 ` [PATCH v2 2/2] dmaengine: tegra210-adma: Add memcpy support Nicolin Chen
2016-09-06 11:52 ` Jon Hunter
2016-09-06 17:21 ` Nicolin Chen
2016-09-06 11:33 ` [PATCH v2 0/2] Add memcpy support for tegra210-adma Jon Hunter
2016-09-06 12:03 ` Dmitry Osipenko
2016-09-06 13:04 ` Jon Hunter [this message]
2016-09-06 13:46 ` Jon Hunter
2016-09-06 14:27 ` Dmitry Osipenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6f45ff6e-5fa7-7aca-154c-85cf235aa62f@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=digetx@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicoleotsuka@gmail.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=vinod.koul@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox