From: Mark Brown <broonie@sirena.org.uk>
To: Oliver Ford <ipaqlinux@oliford.co.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: Problem setting mixer switch with amixer/alsactl.
Date: Wed, 22 Oct 2008 21:57:30 +0100 [thread overview]
Message-ID: <20081022205729.GD7537@sirena.org.uk> (raw)
In-Reply-To: <48FF7538.3090000@oliford.co.uk>
On Wed, Oct 22, 2008 at 07:47:20PM +0100, Oliver Ford wrote:
> 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?
Please send an alsactl save file with the offending configuration - I'll
try to reproduce (though possibly not before Monday).
Could you please also expand on "audio stops working" - for example, do
you get any diagnostics in dmesg, do applications appear to think they
are running normally, is there any noise at all (eg, static) and do any
other audio paths work?
> 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?
The recommended approach is to do this from user space. Direct register
writes when probing should also do the trick if you want to do it
in-kernel but it's not so robust against future changes.
next prev parent reply other threads:[~2008-10-22 20:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 18:47 Problem setting mixer switch with amixer/alsactl Oliver Ford
2008-10-22 20:57 ` Mark Brown [this message]
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=20081022205729.GD7537@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=ipaqlinux@oliford.co.uk \
/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