All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Laura Abbott <labbott@redhat.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
	alsa-devel@alsa-project.org,
	"linux-kernel@vger.kernel.org >> Linux Kernel Mailing List"
	<linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] Headphones no longer working on MacPro6,1 with 4.4
Date: Mon, 06 Jun 2016 16:30:51 +0200	[thread overview]
Message-ID: <s5hk2i2mlt0.wl-tiwai@suse.de> (raw)
In-Reply-To: <7223d50d-9c89-3510-085c-6757feece8a1@redhat.com>

On Thu, 02 Jun 2016 23:20:24 +0200,
Laura Abbott wrote:
> 
> On 05/24/2016 10:54 AM, Takashi Iwai wrote:
> > On Tue, 24 May 2016 18:41:06 +0200,
> > Laura Abbott wrote:
> >>
> >> Node 0x10 [Pin Complex] wcaps 0x40058d: Stereo Amp-Out
> >>   Control: name="Headphone Playback Switch", index=0, device=0
> >>     ControlAmp: chs=3, dir=Out, idx=0, ofs=0
> >>   Amp-Out caps: ofs=0x42, nsteps=0x42, stepsize=0x03, mute=1
> >>   Amp-Out vals:  [0x42 0x42]
> >>   Pincap 0x0000001c: OUT HP Detect
> >>   Pin Default 0x002b4020: [Jack] HP Out at Ext N/A
> >>     Conn = Comb, Color = Green
> >>     DefAssociation = 0x2, Sequence = 0x0
> >>   Pin-ctls: 0xc0: OUT HP
> >>   Unsolicited: tag=01, enabled=1
> >>   Power states:  D0 D3 EPSS
> >>   Power: setting=D3, actual=D3
> >
> > This pin is powered off, because...
> >
> >> 	control.18 {
> >> 		iface CARD
> >> 		name 'Mic Jack'
> >> 		value false
> >> 		comment {
> >> 			access read
> >> 			type BOOLEAN
> >> 			count 1
> >> 		}
> >> 	}
> >> 	control.19 {
> >> 		iface CARD
> >> 		name 'Line Out Phantom Jack'
> >> 		value true
> >> 		comment {
> >> 			access read
> >> 			type BOOLEAN
> >> 			count 1
> >> 		}
> >> 	}
> >> 	control.20 {
> >> 		iface CARD
> >> 		name 'Headphone Jack'
> >> 		value false
> >
> > The headphone jack isn't detected.
> > Meanwhile,
> >
> >> 	control.22 {
> >> 		iface CARD
> >> 		name 'SPDIF Jack'
> >> 		value true
> >
> > SPDIF jack is detected.  This might confuse PA.
> >
> > In anyway, the alsa-info.sh output you gave doesn't help for analyzing
> > the issue while the headphone is plugged.  It is off when unplugged.
> > It's the designed behavior.
> >
> > So, please give the information during the headphone is plugged (but
> > still doesn't produce the sound from the headphone).
> >
> >
> > Takashi
> >
> 
> According to the reporter:
> 
> "Actually, that information was when the headphones were plugged in,
> but the detection is incorrect.  (Linux thinks the headphones are
> unplugged, when they are actually plugged in."

It implies that the pin setup mismatches with the actual hardware.
You need to figure out which pin corresponds to the actual I/O by
yourself, e.g. via hdajackretask or other tool.

The apparent regression just revealed the already buggy setup.


Takashi

      reply	other threads:[~2016-06-06 14:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 19:23 [REGRESSION] Headphones no longer working on MacPro6,1 with 4.4 Laura Abbott
2016-03-15 19:38 ` [REGRESSION] Headphones no longer working on MacPro6, 1 " Takashi Iwai
2016-03-15 19:38   ` [REGRESSION] Headphones no longer working on MacPro6,1 " Takashi Iwai
2016-03-15 19:49   ` Takashi Iwai
2016-03-15 19:49     ` Takashi Iwai
2016-05-20 22:27     ` [REGRESSION] Headphones no longer working on MacPro6, 1 " Laura Abbott
2016-05-20 22:27       ` [REGRESSION] Headphones no longer working on MacPro6,1 " Laura Abbott
2016-05-21  6:41       ` [REGRESSION] Headphones no longer working on MacPro6, 1 " Takashi Iwai
2016-05-21  6:41         ` [REGRESSION] Headphones no longer working on MacPro6,1 " Takashi Iwai
2016-05-21  7:42         ` Takashi Iwai
2016-05-24 16:41           ` Laura Abbott
2016-05-24 16:41             ` Laura Abbott
2016-05-24 17:54             ` Takashi Iwai
2016-06-02 21:20               ` [REGRESSION] Headphones no longer working on MacPro6, 1 " Laura Abbott
2016-06-02 21:20                 ` [REGRESSION] Headphones no longer working on MacPro6,1 " Laura Abbott
2016-06-06 14:30                 ` Takashi Iwai [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=s5hk2i2mlt0.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=labbott@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    /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.