All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Herton Ronaldo Krzesinski <herton.krzesinski@canonical.com>
Subject: Re: Kernel 3.2, and "speaker" controlling headphone path
Date: Mon, 16 Jul 2012 11:37:41 +0200	[thread overview]
Message-ID: <5003E0E5.8080007@canonical.com> (raw)
In-Reply-To: <s5hmx30gie5.wl%tiwai@suse.de>

On 07/16/2012 11:33 AM, Takashi Iwai wrote:
> At Wed, 11 Jul 2012 12:50:20 +0200,
> David Henningsson wrote:
>>
>> It seems like on one machine the "Speaker Playback Volume" was part of
>> the headphone path, in combination with PulseAudio this is leading to
>> muted headphones.
>>
>> One of my colleagues wrote a workaround for that specific machine - I'm
>> providing links in case you're interested:
>>
>> The patch:
>> https://launchpadlibrarian.net/109499922/restrict_bass.patch
>>
>> Alsa-info:
>> https://launchpadlibrarian.net/109251353/bad-kernel-yes-headphones.txt
>>
>> Bug link:
>> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/994685
>
> This doesn't happen with the recent kernel, right?
>
> As far as I've tested with hda-emu, 3.6 kernel picks up the headphone
> path as the primary, as this has the least badness value.

Correct. The issue was not present on 3.0 and 3.4. It was present in 3.2 
and 3.3, and fixed with commit 1c4a54b4513c175ba (ALSA: hda/realtek - 
Finer tuning of auto-parser with badness evaluation), but that commit 
felt to risky to just backport/apply to 3.2.


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

      reply	other threads:[~2012-07-16  9:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 10:50 Kernel 3.2, and "speaker" controlling headphone path David Henningsson
2012-07-16  9:33 ` Takashi Iwai
2012-07-16  9:37   ` David Henningsson [this message]

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=5003E0E5.8080007@canonical.com \
    --to=david.henningsson@canonical.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=herton.krzesinski@canonical.com \
    --cc=tiwai@suse.de \
    /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.