From: Dan Aloni <dan@kernelim.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: on-board sound on ASUS TRX-40
Date: Thu, 22 Oct 2020 15:51:00 +0300 [thread overview]
Message-ID: <20201022125100.GB1140455@gmail.com> (raw)
In-Reply-To: <s5hft66bfpb.wl-tiwai@suse.de>
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.
--
Dan Aloni
next prev parent reply other threads:[~2020-10-22 12:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 8:17 on-board sound on ASUS TRX-40 Dan Aloni
2020-10-22 9:14 ` Takashi Iwai
2020-10-22 10:18 ` Dan Aloni
2020-10-22 10:24 ` Takashi Iwai
2020-10-22 12:33 ` Dan Aloni
2020-10-22 12:36 ` Takashi Iwai
2020-10-22 12:51 ` Dan Aloni [this message]
2020-10-22 12:57 ` Takashi Iwai
2020-10-22 15:49 ` Dan Aloni
2020-10-22 16:09 ` Takashi Iwai
2020-10-22 18:08 ` Dan Aloni
2020-11-04 11:03 apt-ghetto
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=20201022125100.GB1140455@gmail.com \
--to=dan@kernelim.com \
--cc=alsa-devel@alsa-project.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).