From: Greg KH <gregkh@linuxfoundation.org>
To: Doug Kingston <dpk@randomnotes.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: USB Sound Device detection problem
Date: Tue, 19 Jan 2021 19:34:53 +0100 [thread overview]
Message-ID: <YAcmTSV6/fCMCXUd@kroah.com> (raw)
In-Reply-To: <CAGPaoUucowcpa5k_9VVjnRnrUkiG=npiCJYaOyT6-Ya7hEfJKg@mail.gmail.com>
On Tue, Jan 19, 2021 at 10:20:34AM -0800, Doug Kingston wrote:
> I am doing some work setting up some radio data nodes that use USB
> soundcard devices to attach to radios. I am building a system with
> two radios and two identical soundcard devices attached to a Raspberry
> Pi running Raspbian. The devices are discovered at boot time by the
> hid-generic subsystem:
>
> (see dmesg output below)
>
> I am accessing the sound devices from Wine via the ALSA stack. The
> problem I have is that
> the product string is identical for both devices and they show up
> identically to the Windows app ("USB PnP Sound Device"). I need to
> find a way to alter this string so that they are different. If they
> were processed by udev I might be able to do something there.
Why do you need the string to be changed?
And why can't you write a udev rule for this?
> The options seem to be:
> 1) fix at kernel usb discovery
Not going to change :)
> 2) somehow fix in the ALSA library (snd_*)
> 3) fix in Wine (mmsys.drv / winealsa.drv/mmdevdrv.c
> 4) somewhere else?
Why not trigger off of the topology of the USB device? That's what
tools do today for multiple devices of the same exact type, which is
really common. All of that can be done in userspace, with a udev rule,
or a script that is run when accessing a USB device by querying where in
the USB physical tree it is located.
> And, we need to do this in a supportable fashion that does not break
> existing users of this subsystem.
Userspace is the key, you have control over that, so why can't it detect
this?
thanks,
greg k-h
next prev parent reply other threads:[~2021-01-19 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 18:20 USB Sound Device detection problem Doug Kingston
2021-01-19 18:34 ` Greg KH [this message]
2021-01-19 19:40 ` Alan Stern
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=YAcmTSV6/fCMCXUd@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dpk@randomnotes.org \
--cc=linux-usb@vger.kernel.org \
/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.