From: Timur Tabi <timur@freescale.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: asoc: fsl_dma_hw_free being called twice at end of playback
Date: Mon, 03 May 2010 16:05:55 -0500 [thread overview]
Message-ID: <4BDF3AB3.4000803@freescale.com> (raw)
In-Reply-To: <8F61234B-3CA5-4553-A956-1722DD53B55F@opensource.wolfsonmicro.com>
Mark Brown wrote:
> On 3 May 2010, at 21:51, Timur Tabi <timur@freescale.com> wrote:
>
>> In my 8610 ASoC driver, I'm seeing the DMA driver's .hw_free
>> function being
>> called twice whenever playback ends. I've added some printk's to
>> demonstrate:
>
> Is this with or without Liam's multiple CODEC work?
With.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2010-05-03 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 20:51 asoc: fsl_dma_hw_free being called twice at end of playback Timur Tabi
2010-05-03 21:02 ` Mark Brown
2010-05-03 21:05 ` Timur Tabi [this message]
2010-05-03 23:57 ` Raymond Yau
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=4BDF3AB3.4000803@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
/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).