All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: SOUND <alsa-devel@alsa-project.org>
Subject: Re: How to annotate USB jacks without jack detection?
Date: Fri, 11 Dec 2020 10:06:19 +0100	[thread overview]
Message-ID: <s5hv9d8pv90.wl-tiwai@suse.de> (raw)
In-Reply-To: <0SY5LQ.NPOPM8PL9XNK1@canonical.com>

On Fri, 11 Dec 2020 08:14:24 +0100,
Kai-Heng Feng wrote:
> 
> Hi,
> 
> There are some UAC1 devices come with jacks, but without jack
> detection ability. And many USB/Thunderbolt docks are equipped with
> such USB device.
> 
> Userspace like PulseAudio automatically switch to USB audio when they
> gets plugged. However, auto-switching to UAC1 device can be
> problematic because it may not connected to any headset or speaker.
> 
> So I wonder what's the best way to let userspace know the USB device
> is a jack without jack detection ability? Through sysfs or dedicated
> UCM conf?

It's a good question.  AFAIK, that's a long-standing problem, and most
of such devices provide the jack detection via HID, which is,
obviously, a completely different driver.  So, if HID driver actually
creates input devices, we'd need to associate them with the sound card
somehow (likely in user-space).  But I have no clear idea what's the
best approach yet.

Also, I'm not sure whether HID device really gives the right jack
detection event.  A cheap UAC1 device I have here doesn't seem to give
the jack detection but only the mute/volume events, as it seems...

OTOH, there are some UAC2 devices providing the jack detection in the
USB-audio interface, and they seem work as is of now.


thanks,

Takashi

  reply	other threads:[~2020-12-11  9:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11  7:14 How to annotate USB jacks without jack detection? Kai-Heng Feng
2020-12-11  9:06 ` Takashi Iwai [this message]
2020-12-11 12:31   ` Kai-Heng Feng

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=s5hv9d8pv90.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=kai.heng.feng@canonical.com \
    /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.