All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: alsa-devel@alsa-project.org
Subject: Re: Headphone jack and auto-mute of speak output
Date: Thu, 07 Oct 2010 18:03:43 +0200	[thread overview]
Message-ID: <4CADEF5F.7070600@canonical.com> (raw)
In-Reply-To: <AANLkTim-R=FGHo-CxT=gxysisTRT3T35pyrfu7HscKAQ@mail.gmail.com>

On 2010-10-07 15:43, Raymond Yau wrote:
> 2010/10/7 Davyd McColl<davydm@gmail.com>
>
>> Good day
>>
>> I'm new to this list (though I've done some searching, I'm sure I could
>> have
>> missed something), so please bear with me.
>>
>> I filed a bug report recently against Ubuntu with respect to the problem
>> I'm
>> experiencing (as per the subject: jacking in my headphones doesn't mute the
>> speaker output) and was informed that the decision had been made upstream
>> as
>> a design intention. I was linked off to:
>>
>> http://mailman.alsa-project.org/pipermail/alsa-devel/2010-August/030071.html
>> with respect to the thread on this topic. I'd like to raise it again
>> though,
>> perhaps as a configurable feature, for the following reasons:
>>
>
> Enable auto-muting in model=auto only for devices with HP and speakers.
>
> http://git.alsa-project.org/?p=alsa-kernel.git;a=commitdiff;h=2a2ed0dfc9ec44a899c7d4672f73f2c045099118;hp=299f293b3428ae6d73406642cd7d41f08d524c83
>
>
> if the bios set your laptop 's speaker as line out , you need to implement a
> new model for your laptop ,

Can't you just override the pin config (via user_pin_configs in sysfs, 
or a patch file) in this case?

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

  parent reply	other threads:[~2010-10-07 16:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07 11:55 Headphone jack and auto-mute of speak output Davyd McColl
2010-10-07 13:43 ` Raymond Yau
2010-10-07 14:01   ` Davyd McColl
2010-10-07 16:03   ` David Henningsson [this message]
2010-10-07 23:05     ` Raymond Yau
2010-10-08  5:50       ` Davyd McColl
2010-10-09  8:53         ` 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=4CADEF5F.7070600@canonical.com \
    --to=david.henningsson@canonical.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 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.