On Thu, 22 Oct 2020 14:51:00 +0200, Dan Aloni wrote: > > On Thu, Oct 22, 2020 at 02:36:16PM +0200, Takashi Iwai wrote: > > On Thu, 22 Oct 2020 14:33:47 +0200, > > Dan Aloni wrote: > > > > > > On Thu, Oct 22, 2020 at 12:24:31PM +0200, Takashi Iwai wrote: > > > > On Thu, 22 Oct 2020 12:18:52 +0200, > > > > Dan Aloni wrote: > > > > > > > > > > On Thu, Oct 22, 2020 at 11:14:03AM +0200, Takashi Iwai wrote: > > > > > > On Thu, 22 Oct 2020 10:17:46 +0200, > > > > > > Dan Aloni wrote: > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > The on-board earphone jack does not seem to work on an ASUS TRX-40 > > > > > > > board. Here's the alsa-info.sh output: > > > > > > > > > > > > > > http://alsa-project.org/db/?f=7a94c1b1eec4b2e623c75770364ec43c33d6c95c > > > > > > > > > > > > > > Tried coding up the patch below, but it _does not_ fix the problem. It > > > > > > > does shows the earphone as 'plugged' though. Verified that it's not an > > > > > > > hardware issue via Windows. > > > > > > > > > > > > > > Please instruct on how to debug this further. > > > > > > > > > > > > Did you try to add connector_map, too? > > > > > > > > > > Yes, and it did not help. Anything else I can try? > > > > > > > > Well, you need to figure out via trial and error. > > > > It should receive some event processed in > > > > snd_usb_mixer_interrupt_v2(), and you can check which widget is > > > > involved, at least. > > > > > > Upon plugging or unplugging the headphone, the unitid of 11 matches the > > > unit in `trx40_mobo_connector_map`, although two events are happening - > > > two for plug and two for unplug. There's another event for '7', and > > > changing the second item of `static const struct usbmix_connector_map` > > > from 11 to 7 does not seem to affect it. > > > > Well, then I'm afraid that it has yet another mapping of the units. > > You'd need to create the whole map from the topology, and rewrite the > > connector_map as well. > > Would be helpful a USB trace from KVM, when running a Windows VM that > successfully manages this device following USB redirection? I can > produce this given instructions, if you have them handy. The topology is found in lsusb -v output. It's the connection among units. More importantly, the maps only care about the certain units like input/output terminals and feature unit. You can look at those and correct the corresponding unit ids. Takashi
