alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Philip Chu <Philip.Chu@logicpd.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: ALSA driver fails to creat ControlC1 and others...
Date: Fri, 14 Jan 2011 09:31:59 +0100	[thread overview]
Message-ID: <s5h1v4fga2o.wl%tiwai@suse.de> (raw)
In-Reply-To: <0520A3FE5EDCF24F88B3F1451CFC64AE03E397B635@EDPREX01.logicpd.com>

At Thu, 13 Jan 2011 18:17:24 -0600,
Philip Chu wrote:
> 
> I am having problem creating 2nd ALSA sound card driver I developed:
> 
> I found snd_ctl_dev_register() in control.c is called successfully but I do not see the 2nd sound card entry below:
> 
> # ls /dev/snd
> controlC0  pcmC0D0c   pcmC0D0p   pcmC0D1c   seq        timer
> 
> And I saw a suspicious message at the end of boot steps:
> 
> Unmuting sound device: [FAIL]
> Starting dropbear sshd: OK
> 
> 
> Well, this happens with one file system, and with another file system, the 2nd card entry is created correctly as below:
> 
> # ls /dev/snd
> controlC0  pcmC0D0c   pcmC1D1c   seq
> controlC1  pcmC0D0p   pcmC1D1p   timer
> 
> And I don't see that message.
> 
> 
> Anybody has some suggestions?

udev?


Takashi

  reply	other threads:[~2011-01-14  8:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 17:19 [PATCH 4/4] ASoC: soc core allow machine driver to register the card Koul, Vinod
2011-01-13 23:41 ` Mark Brown
2011-01-14  0:17   ` ALSA driver fails to creat ControlC1 and others Philip Chu
2011-01-14  8:31     ` Takashi Iwai [this message]
2011-01-18 16:37       ` Philip Chu
2011-01-14  4:24   ` [PATCH 4/4] ASoC: soc core allow machine driver to register the card Koul, Vinod
2011-01-14 10:52     ` Mark Brown
2011-01-14 11:25       ` Koul, Vinod
2011-01-14 11:37         ` Mark Brown
2011-01-14 13:52           ` Koul, Vinod

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=s5h1v4fga2o.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=Philip.Chu@logicpd.com \
    --cc=alsa-devel@alsa-project.org \
    /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).