From: Patrick Lai <plai@codeaurora.org>
To: alsa-devel <alsa-devel@alsa-project.org>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>
Subject: Problem with snd_soc_suspend
Date: Sun, 13 May 2012 23:30:29 -0700 [thread overview]
Message-ID: <4FB0A685.3040408@codeaurora.org> (raw)
Hi,
The CODEC I am working on has multiple digital audio interfaces included
in multiple DAI-LINks. DAILINK X has ignore_suspend flag set and
DAILINK Y has ignore_suspend flag cleared. The problem I encountered is
that as system attempts to enter suspend while DAILINK X is active,
snd_soc_suspend() calls snd_soc_dapm_stream_event(
SND_SOC_DAPM_STREAM_SUSPEND) on inactive DAILINK Y since DAILINK Y
ignore flag is not set. Consequently, CODEC widgets get powered off
even though they should remain powered for DAILINK X.
Kernel version I am working with is 3.0.
Couple questions with respect to this problem
1. Should soc-core check if CODEC DAI is active beside checking
ignore_suspend flag before calling snd_soc_dapm_stream_event()?
I checked latest soc-core.c from kernel 3.4 RC7. The logic is the same
as 3.0
2. Even if snd_soc_dapm_stream_event() is called, DAPM should not power
off widgets that are powered up for DAILINK x. It seems like DAPM has
the logic to only power off AIF widget if stream name of widget matches
CODEC DAI stream name in soc_dapm_stream_event(). I have not gotten
time to debug this problem further. However, is it a known bug on
kernel 3.0. If so, has the problem been addressed in more recent kernel?
Thanks
Patrick
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next reply other threads:[~2012-05-14 6:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 6:30 Patrick Lai [this message]
2012-05-14 8:34 ` Problem with snd_soc_suspend Mark Brown
2012-05-17 20:21 ` Patrick Lai
2012-05-17 21:46 ` 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=4FB0A685.3040408@codeaurora.org \
--to=plai@codeaurora.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.