On Friday 17 August 2012 11:04 PM, Stephen Warren wrote:

On 08/17/2012 09:17 AM, Stephen Warren wrote:

quoted

On 08/17/2012 12:38 AM, Laxman Dewangan wrote:

quoted

On Thursday 16 August 2012 11:23 PM, Stephen Warren wrote:

quoted

On 08/16/2012 08:13 AM, Laxman Dewangan wrote:

quoted

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.