From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
"perex@perex.cz" <perex@perex.cz>,
Stephen Warren <swarren@nvidia.com>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>, "lrg@ti.com" <lrg@ti.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH] ASoC: tegra: use dmaengine based dma driver
Date: Mon, 2 Jul 2012 13:55:58 +0530 [thread overview]
Message-ID: <4FF15B16.9020903@nvidia.com> (raw)
In-Reply-To: <4FEF166D.2010705@nvidia.com>
On Saturday 30 June 2012 08:38 PM, Laxman Dewangan wrote:
> On Friday 29 June 2012 10:32 PM, Stephen Warren wrote:
>> On 06/29/2012 05:34 AM, Laxman Dewangan wrote:
>>> Use the dmaengine based Tegra APB DMA driver for
>>> data transfer between SPI fifo and memory in
>>> place of legacy Tegra APB DMA.
>>>
>>> Because generic soc-dmaengine-pcm uses the DMAs API
>>> based on dmaengine, using the exported APIs provided
>>> by this generic driver.
>>>
>>> The new driver is selected if legacy driver is not
>>> selected and new dma driver is enabled through config
>>> file.
>> This works just fine with the existing non-dmaengine DMA driver enabled.
>>
>> However, I can't get it to work with dmaengine:
>>
>>> # aplay ~/abba-dq-48000-stereo.wav
>>> [ 151.613476] tegra20-i2s tegra20-i2s.0: dmaengine pcm open failed with err -6
>>> [ 151.620557] tegra20-i2s tegra20-i2s.0: can't open platform tegra20-i2s.0: -6
>>> aplay: main:654: audio open error: No such device or address
> With the error, it seems that dmachannel is not getting allocated.
>
>> I do have the following in my local tree:
>> 68a67b8 ARM: tegra: add device tree AUXDATA for APBDMA
>> 0db7a96 ARM: tegra: dma: rename driver name for clock to "tegra-apbdma"
>>
> Some dma changes which I sent and already on linux-next are also require
> with the above change.
> Alsong with that I have local change like to rename the dma driver to
> compatible with dts files (remove -new from driver).
>
> I think I should send that patches so that you can test it by:
> - Taking already applied dma driver change in linux-next.
> - Apply my new patches which I am going to send.
>
> And do local change in the tegra_defconfig to disable SYSTEM_DMA and
> enable dmaengine based dma driver.
>
>
The new dma patches are:
dma: tegra: fix residual calculation for cyclic case
dma: tegra: rename driver and compatible to match with dts
You require dma changes which is already in linux-next:
dma: tegra: set DMA_CYCLIC capability
dma: tegra: do not set transfer desc flag to DMA_CTRL_ACK in cyclic mode
dma: tegra: add clk_prepare/clk_unprepare
dma: tegra: use sg_dma_address() for getting dma buffer address
dma: tegra: add dmaengine based dma driver
next prev parent reply other threads:[~2012-07-02 8:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 11:34 [PATCH] ARM: tegra: apbio: " Laxman Dewangan
2012-06-29 11:34 ` [PATCH] ASoC: tegra: " Laxman Dewangan
2012-06-29 17:02 ` Stephen Warren
2012-06-30 15:08 ` Laxman Dewangan
2012-07-02 8:25 ` Laxman Dewangan [this message]
2012-07-02 16:45 ` Stephen Warren
2012-07-02 16:47 ` Mark Brown
2012-07-03 6:26 ` Laxman Dewangan
2012-07-18 8:59 ` Laxman Dewangan
2012-07-02 16:46 ` Stephen Warren
2012-07-03 6:29 ` Laxman Dewangan
2012-07-03 10:09 ` Mark Brown
2012-07-03 19:07 ` Mark Brown
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=4FF15B16.9020903@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lrg@ti.com \
--cc=perex@perex.cz \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=tiwai@suse.de \
/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
Powered by JetHome