All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Eric Holstege <eric_holstege@yahoo.com>
Cc: alsa-devel@alsa-project.org, clemens@ladisch.de
Subject: Re: explicit commandline control of speakers vs	headphone output
Date: Fri, 27 Aug 2010 21:26:37 +0200	[thread overview]
Message-ID: <4C78116D.9040704@canonical.com> (raw)
In-Reply-To: <210284.64008.qm@web50707.mail.re2.yahoo.com>

2010-08-27 20:46, Eric Holstege skrev:
> Thanks, Clemens;
> 
> How were you able to determine that from the "amixer scontents" output.
> 
> Although I can't disable *automatic* speaker mute on headphone 
> insertion, can I explicitly unmute them again (e.g. with amixer sset or 
> cset)?
> 
> If not....
> "cat /proc/asound/card*/codec*" says it is the Realtek ALC888.
> Does this mean I have to somehow patch the kernel sound module file
> .../linux-source-2.6.*/sound/pci/hda/patch_realtek.c
> to fix this somehow?

So in the long run, I think it would be better to leave all auto-muting
to userspace. Then stuff like pulseaudio could to advanced decision of
how to handle input events. But that's the long way.

There are certainly ways to disable auto-muting for Realtek ALC888, look
along the lines of "speaker_automute" and "unsol_event". It is also
possible that you could tweak your user_pin_config to trick your HP out
into a Line Out. That way it won't automute, and you don't have to
recompile your kernel.

As a side note: The VIA HDA driver, I believe, have an option for
turning automute off. But it also sets "mute" on a misnamed control at
the same time, tricking PA into believing that you want to mute all
output. So PA is "helpful" and mutes everything else as well. :-/

-- 
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic

  reply	other threads:[~2010-08-27 19:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-27 18:46 explicit commandline control of speakers vs headphone output Eric Holstege
2010-08-27 19:26 ` David Henningsson [this message]
2010-08-27 23:26   ` Raymond Yau
2010-08-28  8:02 ` Raymond Yau
  -- strict thread matches above, loose matches on Subject: below --
2010-08-27 19:49 Eric Holstege
2010-08-27 14:18 Eric Holstege
2010-08-27 16:48 ` Clemens Ladisch
2010-08-26 18:40 Eric Holstege
2010-08-27  6:26 ` Clemens Ladisch
2010-08-25 16:41 Eric Holstege
2010-08-25 22:48 ` Raymond Yau

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=4C78116D.9040704@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=eric_holstege@yahoo.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.