alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Rajeev kumar <rajeev-dlh.kumar@st.com>
To: "Péter Ujfalusi" <peter.ujfalusi@ti.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: Linux Kernel-3.5 crashed as dapm is not supported by codec
Date: Fri, 9 Nov 2012 16:47:07 +0530	[thread overview]
Message-ID: <509CE633.1070002@st.com> (raw)
In-Reply-To: <509BC3EC.4030503@ti.com>

Hello Peter,

On 11/8/2012 8:08 PM, Péter Ujfalusi wrote:
> On 11/06/2012 11:40 AM, Rajeev kumar wrote:
>> 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"),
>> };
>>
>> static const struct snd_soc_dapm_route sta529_audio_map[] = {
>>          {"DAC", NULL, "output"},
>>          {"ADC", NULL, "input"},
>>          {"HPL", NULL, "HP Left Out"},
>>          {"HPR", NULL, "HP Right Out"},
>>          {"SPKL", NULL, "SPK Left Out"},
>>          {"SPKR", NULL, "SPK Right Out"},
>> };
>
> If this is all you have for DAPM routing I just wonder what the core will do
> with these... I mean you don't appear to have valid routing: no sign of
> "output", "input", "HP Left Out", etc.
>
> But it is really odd that you can not have at least some power control bits
> along the paths.

Yes I have a single bit in a register which will do power bridge 
OFF/ONN. Right now depending on biasing level this bit is getting 
manipulated.

With the DAPM macros how can I control this bit? Please share your opinion.

>
> This would look odd also but at least connects the widgets:
> static const struct snd_soc_dapm_route sta529_audio_map[] = {
>          {"HPL", NULL, "DAC"},
>          {"HPR", NULL, "DAC"},
>          {"ADC", NULL, "MIC1"},
> };


>
> Don't you have messages during boot or module loading about DAPM route error?
>

Right now I am working on it. Yes with the given sta529_dapm_widgets and 
audio_map I am getting "Failed to add route output->DAC". I have to work 
on this.

With the sta529_audio_map suggested by you, There is no any error I am 
getting during boot time. Thanks for your valuable suggestion.

As I dont have any event based dapm control, how can I test my dapm 
support whether it is working or not?

Best Regards
Rajeev

      reply	other threads:[~2012-11-09 11:17 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
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 [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=509CE633.1070002@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 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).