From: Laxman Dewangan <ldewangan@nvidia.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: "broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tiwai@suse.de" <tiwai@suse.de>,
"perex@perex.cz" <perex@perex.cz>
Subject: Re: [PATCH] sound: soc: tegra: do not provide PAUSE/RESUME in hardware info
Date: Wed, 3 Apr 2013 15:03:11 +0530 [thread overview]
Message-ID: <515BF757.3030507@nvidia.com> (raw)
In-Reply-To: <515C03BC.3040301@metafoo.de>
On Wednesday 03 April 2013 03:56 PM, Lars-Peter Clausen wrote:
> On 04/03/2013 11:19 AM, Laxman Dewangan wrote:
>> Tegra PCM driver uses the dmaengine based DMA driver and Tegra DMA
>> driver does not support the pause/resume functionality as hardware
>> does not support it.
>>
>> ALSA driver support the sw based pause/resume functionality if hardware
>> does not support it and in this case, hw driver should not provide
>> the hardware info with PAUSE/RESUME bit enable.
>>
>> Remmoving the SNDRV_PCM_INFO_PAUSE and SNDRV_PCM_INFO_RESUME from hardware
>> info and using the snd_dmaengine_pcm_trigger() for pcm_trigger callback.
>>
>> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> Hm, I sent out the same patch just half an our or so ago.
>
Then I lost the race. I was struggling with sdcard until I bought the
new one.
prev parent reply other threads:[~2013-04-03 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 9:19 [PATCH] sound: soc: tegra: do not provide PAUSE/RESUME in hardware info Laxman Dewangan
2013-04-03 10:26 ` Lars-Peter Clausen
2013-04-03 9:33 ` Laxman Dewangan [this message]
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=515BF757.3030507@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=perex@perex.cz \
--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