From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "olof@lixom.net" <olof@lixom.net>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"lrg@ti.com" <lrg@ti.com>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
"vinod.koul@linux.intel.com" <vinod.koul@linux.intel.com>,
"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 1/5] ARM: tegra: config: enable dmaengine based APB DMA driver
Date: Fri, 17 Aug 2012 11:34:50 -0600 [thread overview]
Message-ID: <502E80BA.5020409@wwwdotorg.org> (raw)
In-Reply-To: <502E60A3.1020405@wwwdotorg.org>
On 08/17/2012 09:17 AM, Stephen Warren wrote:
> On 08/17/2012 12:38 AM, Laxman Dewangan wrote:
>> On Thursday 16 August 2012 11:23 PM, Stephen Warren wrote:
>>> On 08/16/2012 08:13 AM, Laxman Dewangan wrote:
>>>> Enable config for dmaengine based Tegra APB DMA driver and
>>>> disable the legacy APB DMA driver (SYSTEM_DMA).
>>> Laxman, if I apply this series to next-20120816 (plus a few patches in
>>> my local work branch plus the CPU hotplug patches from Joseph, although
>>> I suspect none of that matters), then audio playback on Tegra20 is
>>> broken; the pitch is far too high. Audio playback on Tegra30 works as
>>> expected.
>>
>> I run the test again on ventana and did not see any issue.
>> I play one song and saw similar behavior with/without this series.
>
> OK, I'll test some other boards. I tested Whistler, although all the
> clocking logic is identical between all Tegra20 boards.
I tested both 3.6-rc2 and next-20120816, and they both work fine on Ventana.
I then applied this patch series to both (plus your "dma: tegra:
enable/disable dma clock" for 3.6-rc2) and it causes (or at least
exposes) the problem.
All testing was with a full git clean, using tegra_defconfig, and with
no other patches applied.
If you're not seeing this problem, are you sure you're executing the
kernel you think you are, and that it got correctly switched to the new
dmaengine driver, and rebuilt after applying your patches?
next prev parent reply other threads:[~2012-08-17 17:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 14:13 [PATCH 0/5] ARM: tegra: move all APB DMA client to dmaengine based driver Laxman Dewangan
2012-08-16 14:13 ` [PATCH 1/5] ARM: tegra: config: enable dmaengine based APB DMA driver Laxman Dewangan
2012-08-16 17:53 ` Stephen Warren
2012-08-17 6:38 ` Laxman Dewangan
2012-08-17 15:17 ` Stephen Warren
2012-08-17 17:34 ` Stephen Warren [this message]
2012-08-17 18:00 ` Laxman Dewangan
2012-08-16 14:13 ` [PATCH 2/5] ARM: tegra: dma: remove legacy " Laxman Dewangan
2012-08-16 14:13 ` [PATCH 3/5] ARM: tegra: apbio: remove support of legacy DMA driver based access Laxman Dewangan
2012-08-16 14:13 ` [PATCH 4/5] spi: tegra: " Laxman Dewangan
2012-09-06 23:50 ` Stephen Warren
2012-09-14 15:57 ` Mark Brown
2012-09-14 15:57 ` Stephen Warren
2012-09-14 16:02 ` Mark Brown
2012-09-13 23:36 ` Stephen Warren
2012-08-16 14:13 ` [PATCH 5/5] ASoC: " Laxman Dewangan
2012-09-06 23:50 ` Stephen Warren
2012-09-14 15:57 ` Stephen Warren
2012-09-14 16:08 ` Mark Brown
2012-09-13 23:36 ` Stephen Warren
2012-09-14 15:53 ` Mark Brown
2012-09-14 16:00 ` Stephen Warren
2012-09-14 16:33 ` Mark Brown
2012-09-13 23:35 ` [PATCH 0/5] ARM: tegra: move all APB DMA client to dmaengine based driver Stephen Warren
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=502E80BA.5020409@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lrg@ti.com \
--cc=olof@lixom.net \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=vinod.koul@linux.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).