All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Sergey 'Jin' Bostandzhyan <jin@mediatomb.cc>
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] Surround speaker connection on Acer 8951G
Date: Thu, 05 Sep 2019 17:07:07 +0200	[thread overview]
Message-ID: <s5ha7bipysk.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190902213912.GA6630@xn--80adja5bqm.su>

On Mon, 02 Sep 2019 23:39:12 +0200,
Sergey 'Jin' Bostandzhyan wrote:
> 
> > One thing to be improved would be to drop the surround jack control.
> > Adjust the pin config to different value with the fixed pin
> > connection, so that the auto-parser won't create the "Surround Jack"
> > control.  This isn't needed by PA or else, otherwise it may be
> > confusing.
> 
> Hmm, if I understand you correctly, then you are referring to bits 31:30
> Port Connectivity? 
> 
> It does not seem to work that way... I tried all combinations and I either
> lose jack detect support or I lose the 5.1 profile in Pulse.
> 
> With these settings snd_hda_jack_detect_state() never returns HDA_JACK_PRESENT:
> 0x91130012 [Fixed] Speaker at Int Rear
> 0xd1130012 [Both] Speaker at Int Rear
> 
> I can plug or unplug, I get called, but I always receive HDA_JACK_PHANTOM
> 
> snd_hda_jack_detect_state() works fine with "no physical connection to port":
> 0x51130012 [N/A] Speaker at Int Rear
> 
> But with the above pin setting I "lose" the 5.1 profile in Pulse...
> 
> Which leaves me with with what I had before:
> 0x11130012 [Jack] Speaker at Int Rear
> 
> Am I missing something or did you mean some other setting? Should I be
> using a different function instead of snd_hda_jack_detect_state() to
> check my jack state in the callback?

OK, this would be really tricky to work around it.  It's merely a jack
control that won't be referred by PA, so we can live with it, unless
you see any obvious side effect.

So, when the patch is ready for submission, feel free to send it.


thanks,

Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2019-09-05 15:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 19:24 Surround speaker connection on Acer 8951G Sergey 'Jin' Bostandzhyan
2019-07-19 11:12 ` Sergey 'Jin' Bostandzhyan
2019-07-19 14:44   ` Takashi Iwai
2019-07-20 16:54     ` Sergey 'Jin' Bostandzhyan
2019-08-19 19:57       ` Sergey 'Jin' Bostandzhyan
2019-08-22 14:17         ` Takashi Iwai
2019-08-22 20:30           ` Sergey 'Jin' Bostandzhyan
2019-08-29  9:30             ` Takashi Iwai
2019-08-29 10:38               ` Sergey 'Jin' Bostandzhyan
2019-08-29 11:29                 ` Takashi Iwai
2019-08-30 11:45                   ` Sergey 'Jin' Bostandzhyan
2019-08-30 11:45                     ` [alsa-devel] " Sergey 'Jin' Bostandzhyan
2019-08-30 12:22                     ` Takashi Iwai
2019-08-30 12:22                       ` [alsa-devel] " Takashi Iwai
2019-09-01 19:27                       ` Sergey 'Jin' Bostandzhyan
2019-09-01 19:27                         ` [alsa-devel] " Sergey 'Jin' Bostandzhyan
2019-09-02  6:41                         ` Takashi Iwai
2019-09-02  6:41                           ` [alsa-devel] " Takashi Iwai
2019-09-02 21:39                           ` Sergey 'Jin' Bostandzhyan
2019-09-05 15:07                             ` Takashi Iwai [this message]
2019-09-06  9:33                               ` [alsa-devel] [PATCH] Add Acer Aspire Ethos 8951G model quirk Sergey Bostandzhyan
2019-09-06 12:13                                 ` Takashi Iwai
2019-11-25 17:39                     ` [alsa-devel] Surround speaker connection on Acer 8951G Sergey 'Jin' Bostandzhyan
2019-11-27 11:28                       ` Takashi Iwai
2019-11-27 16:17                         ` Sergey 'Jin' Bostandzhyan
2019-11-27 16:41                           ` Takashi Iwai
2019-11-28 15:46                             ` Sergey 'Jin' Bostandzhyan

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=s5ha7bipysk.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jin@mediatomb.cc \
    /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.