From: edes <edes@gmx.net>
To: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Johan Hovold <johan@kernel.org>, Takashi Iwai <tiwai@suse.de>
Subject: Re: kernel 5.4.11: problems with usb sound cards
Date: Sun, 2 Feb 2020 20:28:16 -0300 [thread overview]
Message-ID: <20200202202816.5a1d8af1@acme7.acmenet> (raw)
In-Reply-To: <20200202134159.GM10381@localhost>
el 2020-02-02 a las 14:41 Johan Hovold escribió:
> I realised I forgot the test to match on the device descriptor when
> applying the blacklist. It doesn't matter currently since I only enable
> the quirk for your device, but if you haven't tested the patch already,
> would you mind testing the below patch instead?
Hi, Johan, thank you for looking into this. I tested your patch, and it
works! (5.4.11 and 5.5.0).
I haven't performed extensive tests, but the card is again recognized as
both playback and capture device. Thank you!
Is this and acceptable solution and will this patch be integrated into the
kernel?
OTOH, you said:
> Ok, so the device has a broken altsetting 3 for interface 1, where
> endpoint 0x85 is declared as an isochronous endpoint, despite being used
> by interface 2 as an audio endpoint:
[...]
> Note that the broken altsetting probably should be using endpoint 0x81
> just like the other altsettings for that interface,
I can't say I understand exactly what you're saying, but do you think it
could be worth contacting the company and see if they are willing to fix
this with a new firmware?
Anyway, it's working now, thank you again.
--
next prev parent reply other threads:[~2020-02-02 23:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 13:58 kernel 5.4.11: problems with usb sound cards edes
2020-02-01 14:10 ` Johan Hovold
2020-02-01 16:26 ` edes
2020-02-02 10:19 ` Johan Hovold
2020-02-02 13:41 ` Johan Hovold
2020-02-02 23:28 ` edes [this message]
2020-02-03 7:57 ` Takashi Iwai
2020-02-03 8:29 ` Johan Hovold
2020-02-03 9:54 ` Takashi Iwai
2020-02-03 8:42 ` Johan Hovold
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=20200202202816.5a1d8af1@acme7.acmenet \
--to=edes@gmx.net \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.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