From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Rajeev kumar <rajeev-dlh.kumar@st.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Linux Kernel-3.5 crashed as dapm is not supported by codec
Date: Wed, 7 Nov 2012 15:56:07 +0100 [thread overview]
Message-ID: <20121107145606.GJ20844@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5099F265.6010008@st.com>
[-- Attachment #1.1: Type: text/plain, Size: 1867 bytes --]
On Wed, Nov 07, 2012 at 11:02:21AM +0530, Rajeev kumar wrote:
> Turn on logging does not helping in giving any extra information in
> this case. Backtracing the code gives me the line number. Please
> find below the information.
Perhaps if you were to share the logging someone might spot something,
or perhaps if you thought about the logging in more detail...
> static void soc_dapm_shutdown_codec(struct snd_soc_dapm_context *dapm)
> 3540 {
> 3541 struct snd_soc_dapm_widget *w;
> 3542 LIST_HEAD(down_list);
> 3543 int powerdown = 0;
> 3544
> 3545 list_for_each_entry(w, &dapm->card->widgets, list) {
> 3546 if (w->dapm != dapm)
> 3547 continue;
> 3548 if (w->power) {
> 3549 dapm_seq_insert(w, &down_list, false);
> 3550 w->power = 0;
> 3551 powerdown = 1;
> 3552 }
> 3553 }
> If you check line number 3545, it is trying to get widget from card.
> and the system get crashed as there is no entry for dapm in the card.
Your analysis does not appear to correspond to the code. The DAPM
context is being used to find the card here, not the other way around as
you say. How have we managed to get an active DAPM context which isn't
part of a card?
> As I mentioned previously, I have provided widgets support only at
> codec level not at platform/machine level. So extracting widgets
> from card may create an issue.
> Note:
> Just to make an experiment, I have added a single widget in machine
> driver then also I am getting the same crash log.
So if you've tested this and found that this is not related to having
widgets in the card what is making you continually mention that you
don't have widgets in the card? Having no widgets outside the CODEC is
totally normal.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2012-11-07 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 11:16 Linux Kernel-3.5 crashed as dapm is not supported by codec Rajeev kumar
2012-09-20 11:49 ` Mark Brown
2012-09-21 3:57 ` Rajeev kumar
2012-09-21 11:14 ` Mark Brown
2012-11-06 10:40 ` Rajeev kumar
2012-11-06 11:43 ` Mark Brown
2012-11-07 5:32 ` Rajeev kumar
2012-11-07 14:56 ` Mark Brown [this message]
2012-11-08 4:28 ` Rajeev kumar
2012-11-08 18:18 ` Misael Lopez
2012-11-09 10:44 ` Rajeev kumar
2012-11-08 14:38 ` Péter Ujfalusi
2012-11-09 11:17 ` Rajeev kumar
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=20121107145606.GJ20844@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=peter.ujfalusi@ti.com \
--cc=rajeev-dlh.kumar@st.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;
as well as URLs for NNTP newsgroup(s).