[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <502E86C1.4000800@nvidia.com>
Date: Fri, 17 Aug 2012 23:30:33 +0530
From: Laxman Dewangan <ldewangan@...dia.com>
To: Stephen Warren <swarren@...dotorg.org>
CC: "olof@...om.net" <olof@...om.net>,
"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
"lrg@...com" <lrg@...com>,
"broonie@...nsource.wolfsonmicro.com"
<broonie@...nsource.wolfsonmicro.com>,
"vinod.koul@...ux.intel.com" <vinod.koul@...ux.intel.com>,
"linux@....linux.org.uk" <linux@....linux.org.uk>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
"spi-devel-general@...ts.sourceforge.net"
<spi-devel-general@...ts.sourceforge.net>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>
Subject: Re: [PATCH 1/5] ARM: tegra: config: enable dmaengine based APB DMA
driver
On Friday 17 August 2012 11:04 PM, Stephen Warren wrote:
> 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?
I generally clean, remove .config and then generate .config , build and
test whenever any branch change or want to remove any change. I tested
in next-20120816.
Let me take help from other team member for test it if I am missing
anything here.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists