From: "Palacios, Hector" <Hector.Palacios@digi.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH] ASoC: soc-pcm: always cancel any pending delayed stream shutdown
Date: Tue, 28 Oct 2014 17:42:18 +0000 [thread overview]
Message-ID: <544FD578.7000205@digi.com> (raw)
In-Reply-To: <CAOMZO5BjS9y0sCkT8wq_pdi7BgxB-5PMa8gCdAgs5=CfYP5K1A@mail.gmail.com>
Hi Fabio,
On 10/28/2014 04:23 PM, Fabio Estevam wrote:
> Hi Hector,
>
> On Wed, Oct 22, 2014 at 3:25 PM, Palacios, Hector <Hector.Palacios@digi.com>
> wrote:
>
>>> You're not saying what the problems are, just that they might be caused.
>>
>> Sorry, your right. When I do a recording 2 seconds after a previous playback, and
>> later play the recorded sound I hear 3 seconds of correct audio and then I
>> continue to hear good audio but mixed with noise and at a higher volume, as if
>> the codec had reseted certain parameters to some default values.
>
> Are you able to reproduce this problem on 3.18-rc?
Mark was right and I tracked the problem down to sgtl5000 driver's function
power_vag_event() which is called by the scheduled work 5 seconds after a playback is
finished.
Then I saw this was already fixed in commit f091f3f07328f75d20a2a5970d1f8b58d95fc990
"ASoC: sgtl5000: prevent playback to be muted when terminating concurrent capture".
Thanks
--
Hector Palacios
prev parent reply other threads:[~2014-10-28 17:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 14:14 [PATCH] ASoC: soc-pcm: always cancel any pending delayed stream shutdown Hector Palacios
2014-10-22 16:28 ` Mark Brown
2014-10-22 17:25 ` Palacios, Hector
2014-10-28 15:14 ` Mark Brown
2014-10-28 15:23 ` Fabio Estevam
2014-10-28 17:42 ` Palacios, Hector [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=544FD578.7000205@digi.com \
--to=hector.palacios@digi.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
/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