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: Tue, 6 Nov 2012 12:43:24 +0100 [thread overview]
Message-ID: <20121106114323.GD10080@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <5098E929.7040404@st.com>
[-- Attachment #1.1: Type: text/plain, Size: 1248 bytes --]
On Tue, Nov 06, 2012 at 04:10:41PM +0530, Rajeev kumar wrote:
> Once again I am raising this issue. Sorry for that.
> First time I have implemented dapm support for my codec driver
> (sta529), but still crash is there. There is no any asynchronous
> events, so platform/Machine driver does not contains any dapm
> widgets.
This is probably a bug in your system given that nobody else is seeing
it, I'd suggest you follow normal debugging processes to figure out
where the crash is occuring. Just a backtrace isn't really enough to
provide useful diagnostic information (especially without the
translation to line numbers), you should at least turn on logging and
also translate the backtrace into line numbers.
>
> Please find below the implementation for dapm.
>
> static const struct snd_soc_dapm_widget sta529_dapm_widgets[] = {
> SND_SOC_DAPM_DAC("DAC", "Play", SND_SOC_NOPM , 0, 0),
> SND_SOC_DAPM_ADC("ADC", "Capture", SND_SOC_NOPM, 0, 0),
> SND_SOC_DAPM_OUTPUT("HPL"),
> SND_SOC_DAPM_OUTPUT("HPR"),
> SND_SOC_DAPM_OUTPUT("SPKL"),
> SND_SOC_DAPM_OUTPUT("SPKR"),
> SND_SOC_DAPM_INPUT("MIC1"),
> };
Does the device really have no power control at all?
[-- 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-06 11:43 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 [this message]
2012-11-07 5:32 ` Rajeev kumar
2012-11-07 14:56 ` Mark Brown
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=20121106114323.GD10080@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).