Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Ford <ipaqlinux@oliford.co.uk>
To: alsa-devel@alsa-project.org
Subject: Problem setting mixer switch with amixer/alsactl.
Date: Wed, 22 Oct 2008 19:47:20 +0100	[thread overview]
Message-ID: <48FF7538.3090000@oliford.co.uk> (raw)

Hi,

I have a system with a wm9713 ac97 codec. It has a single speaker 
connected to SPKL and OUT4 in BTL config.

Currently I'm setting up the audio path with a small script using amixer:
amixer cset numid=90 2        # Out4 Mux = Inv2
amixer cset numid=95 3        # Left Speaker Out Mux = Speaker
amixer cset numid=88 2        # DAC Inv Mux 2  = Speaker
amixer cset numid=31 1        # Out4 Playback Switch = on
amixer cset numid=2  1,0      # Speaker Playback Switch = L:on, R:off

and also:
amixer cset numid=62 1        # Speaker Mixer PCM Playback Switch = on

If I do all of the above except for setting 'Speaker Mixer PCM Playback 
Switch' and then un-mute that in the full alsamixer program, the audio 
works through the speaker.  If I run the 'Speaker Mixer PCM Playback 
Switch' amixer command (either before or after setting it with 
alsamixer), the audio stops working. Once that's happened I can't get it 
back at all without a full reboot (even suspend/resume doesn't help).

Setting it with alsamixer so it works and then using alsactl to save and 
restore the config also breaks it.

I'm not sure how to go about debugging this one, can anyone help?

Also, is there a way to (and should I) set the DAC -> SPKMIX -> INV2 -> 
OUT4 etc in my platform definition in the kernel code, rather than doing 
it with amixer?

Oliver Ford

             reply	other threads:[~2008-10-22 18:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-22 18:47 Oliver Ford [this message]
2008-10-22 20:57 ` Problem setting mixer switch with amixer/alsactl Mark Brown
2008-10-22 22:56   ` Oliver Ford
2008-10-23 14:00     ` Mark Brown
2008-10-23 14:07       ` Oliver Ford
2008-10-23 22:55         ` Oliver Ford
2008-10-27 20:44           ` Mark Brown
     [not found]         ` <4900F6D2.6030305@oliford.co.uk>
2008-10-23 23:54           ` Mark Brown
2008-10-24 17:26           ` Mark Brown
2008-10-23 13:27 ` Mark Brown
2008-10-23 13:56   ` Oliver Ford
2008-10-23 14:01     ` Mark Brown
2008-10-23 17:45       ` Robert Jarzmik
2008-10-24 17:25         ` Mark Brown
2008-10-24 19:09           ` Robert Jarzmik
2008-10-24 20:32             ` Mark Brown
2008-10-28 13:10             ` Mark Brown
2008-10-28 15:34               ` Mark Brown
2008-10-28 15:41                 ` Takashi Iwai
2008-10-28 15:48                   ` Mark Brown
2008-10-28 15:54                     ` Takashi Iwai
2008-10-28 21:51                 ` Oliver Ford
2008-10-29 14:53                   ` Mark Brown
2008-10-29 16:04                   ` Mark Brown
2008-10-30 11:40                     ` Mark Brown
2008-10-30 17:47                       ` Oliver Ford

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=48FF7538.3090000@oliford.co.uk \
    --to=ipaqlinux@oliford.co.uk \
    --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