From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: vinod.koul@intel.com, 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 v3 2/2] dmaengine: tegra210-adma: Add memcpy support
Date: Thu, 8 Sep 2016 10:31:42 -0700 [thread overview]
Message-ID: <20160908173141.GA28381@Asurada-Nvidia> (raw)
In-Reply-To: <37d4645c-6318-78bd-79bb-844fb6764a1b@nvidia.com>
On Thu, Sep 08, 2016 at 03:19:57PM +0100, Jon Hunter wrote:
> I tried this again on my audio testing branch for tegra210 and it worked ...
>
> [ 36.427210] dmatest: Started 1 threads using dma1chan0
> [ 37.036948] dmatest: dma1chan0-copy0: summary 1024 tests, 0 failures 2410 iops 19419 KB/s (0)
>
> Do you have other patches in your branch? If so it would be good to
> understand the dependency. May be we are missing a clock somewhere?
Sorry. I forgot to mention that the TEGRA210_CLK_APE_SLCG_OVR
clock is required for the tests. So I cherry-picked 2 patches
from your audio branch to the linux-next:
clk: tegra210: Add SLCG override gate clocks
ARM64: tegra: DT: Add SLCG clock for AUD
Besides these two, there'e merely some straightforward changes
to enable the ADMA in the defconfig and DT.
And it seems that you've submitted that patch once but it got
hold because it wasn't so useful at that time?
Thanks
Nic
next prev parent reply other threads:[~2016-09-08 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 18:42 [PATCH v3 0/2] Add memcpy support for tegra210-adma Nicolin Chen
2016-09-06 18:42 ` [PATCH v3 1/2] dmaengine: tegra210-adma: Add pre-check for cyclic callback Nicolin Chen
2016-09-06 18:42 ` [PATCH v3 2/2] dmaengine: tegra210-adma: Add memcpy support Nicolin Chen
2016-09-08 14:08 ` Jon Hunter
2016-09-08 14:19 ` Jon Hunter
2016-09-08 17:31 ` Nicolin Chen [this message]
2016-09-12 14:34 ` Jon Hunter
2016-09-12 20:50 ` Nicolin Chen
2016-09-13 8:52 ` Jon Hunter
2016-09-14 13:38 ` Vinod Koul
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=20160908173141.GA28381@Asurada-Nvidia \
--to=nicoleotsuka@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).