Re: RfC / [PATCH] Jack sense support for Medion E4254

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 17 Sep 2019 12:18:58 +0200,
Jan-Marek Glogowski wrote:
> 
> >> And for whatever reason jack sense is now working, at least for some normal
> >> output-only headset (currently I don't have one included a mic with me, so
> >> actually can't test that mic volume works correctly).
> >>
> >> I was just wondering, if my pin values are actually correct, because they still
> >> define different association, as I understand it, but the ASUS fix even works
> >> with these wrong channels /associations 2 and 4.
> >>
> >> So the attached patch works for me, but I'm still wondering, if this is the
> >> correct solution. FWIW, jack sense works fine in Windows.
> >>
> >> Anything I might be missing here?
> > 
> > I don't think anything wrong here, as long as your quirk actually
> > works.  I can double-check if I get alsa-info.sh output (run with
> > --no-upload option) with hda-emu, too.
> 
> I've tested this just with the 4.19 kernel used by Debian buster with the
> patched realtek module build as a DKMS package. That kernel code is 4.19.67.
> Then I just moved the code to the right position in the current master kernel.
> It works for me.
> 
> I tried to compile hda-emu, but already the first file in the kernel dir fails
> hard with some missing functions. I used alsa-info.sh with --no-upload, but the
> output starts with upload=true?! I attached the log.

Thanks.  S> 
> 
> Am 16.09.19 um 23:55 schrieb Takashi Iwai:
> > On Mon, 16 Sep 2019 10:38:07 +0200,
> > Jan-Marek Glogowski wrote:
> >>
> >> I recently bought the laptop. It has one jack for attaching a headset. Jack
> >> sense is announced by the HDA config but not working. Except for some
> >> positioning, and color information, the PIN config seemed to be sensible, and
> >> everything I tried to override, didn't result in a working jack.
> >>
> >> Manually unmuting the jack using hda-analyser resulted in working output, so
> >> generally the config seemed to work.
> >>
> >> Reading the patch-realtek code, if found ALC256_FIXUP_ASUS_HEADSET_MODE, which
> >> somehow changed the pin 0x19 to be associated with the 0x21 headset out pin,
> >> resulting in this dmesg change:
> >>
> >> -snd_hda_codec_realtek hdaudioC0D0:      Mic=0x19
> >> +snd_hda_codec_realtek hdaudioC0D0:      Headset Mic=0x19
> > 
> > What are the initial pin config values for these?
> 
> $ cat /sys/class/sound/hwC0D0/init_pin_configs
> 0x12 0x90a60130
> 0x13 0x40000000
> 0x14 0x90170110
> 0x18 0x411111f0
> 0x19 0x02a19040
> 0x1a 0x411111f0
> 0x1b 0x411111f0
> 0x1d 0x4067b945
> 0x1e 0x411111f0
> 0x21 0x02214020

Thanks.  So the problem was that the codec driver created "Front
Headphone Jack" because of the jack location, while there is no
corresponding mute/volume mixer element with that prefix.
Although we can fix in a different way, it'd be a higher breakage
risk, so I take your patch as is.


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



[Index of Archives]     [ALSA User]     [Linux Audio Users]     [Pulse Audio]     [Kernel Archive]     [Asterisk PBX]     [Photo Sharing]     [Linux Sound]     [Video 4 Linux]     [Gimp]     [Yosemite News]

  Powered by Linux