From: Johan Hovold <johan@kernel.org>
To: Oliver Neukum <oneukum@suse.com>
Cc: Ralf Beck <musical_snake@gmx.de>, linux-usb@vger.kernel.org
Subject: Duplicate endpoints (was: Re:)
Date: Mon, 20 Dec 2021 12:30:32 +0100 [thread overview]
Message-ID: <YcBpWMtrk2zQx8mw@hovoldconsulting.com> (raw)
In-Reply-To: <b1001f8a-df10-a3c7-f715-157f5be16fa4@suse.com>
On Mon, Dec 20, 2021 at 11:01:56AM +0100, Oliver Neukum wrote:
>
> On 20.12.21 07:46, Ralf Beck wrote
> > One set with audio class specific interfaces for use by an audi
> > class driver. The other set with vendor specific interfaces for use
> > by the vendor driver. Obviously the class specific interfaces and
> > vendor specific interfaces are not intended to be use by a driver
> > simultaniously.
> Such devices are buggy. We usually define quirks for such devices.
> > There must be another solution to deal with this. It is unacceptable
> > to request a user of these devices to have to disablethe duplicate
> > endpoint check and recompile the kernel on every update in order to
> > be able to use their devices in vendor mode.
> I suggest you write a patch to introduce a quirk that disables one of the
> interfaces and disregards disabled interfaces for purposes of the check.
We already have USB_QUIRK_ENDPOINT_IGNORE (previously known as
USB_QUIRK_ENDPOINT_BLACKLIST) for this. See, for example:
184eead057cc ("USB: core: Fix regression in Hercules audio card")
and
bdd1b147b802 ("USB: quirks: blacklist duplicate ep on Sound Devices USBPre2")
Johan
prev parent reply other threads:[~2021-12-20 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 6:46 Ralf Beck
2021-12-20 7:55 ` Greg KH
2021-12-20 10:01 ` Re: Oliver Neukum
2021-12-20 11:30 ` Johan Hovold [this message]
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=YcBpWMtrk2zQx8mw@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=musical_snake@gmx.de \
--cc=oneukum@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox