From: Rajeev kumar <rajeev-dlh.kumar@st.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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: Fri, 21 Sep 2012 09:27:47 +0530 [thread overview]
Message-ID: <505BE5BB.5010008@st.com> (raw)
In-Reply-To: <20120920114951.GJ17666@opensource.wolfsonmicro.com>
Hello Mark,
On 9/20/2012 5:19 PM, Mark Brown wrote:
> On Thu, Sep 20, 2012 at 04:46:27PM +0530, Rajeev kumar wrote:
>
>> I have not provided the dapm support in codec. When the system goes
>> in hibernation state it gets crashed. command for putting the system
>> in hibernation:
>
> DAPM is mandatory now, though any device with an audio interface
> connected should have some DAPM widgets added transparently so its not
> always explicitly present in the CODEC driver. It's just causing too
> much pain to special case non-DAPM devices and theres really not any
> cases where there's no need for widgets.
>
Is DAPM operates on event? In my device event generation is not
there.Please correct me if I am wrong.
Are there some dummy interface for DAPM? What are those interfaces?
Best Regards
Rajeev
next prev parent reply other threads:[~2012-09-21 3:57 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 [this message]
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
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=505BE5BB.5010008@st.com \
--to=rajeev-dlh.kumar@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=peter.ujfalusi@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.