From: Johan Hovold <johan@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: edes <edes@gmx.net>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan@kernel.org>
Subject: Re: kernel 5.4.11: problems with usb sound cards
Date: Mon, 3 Feb 2020 09:29:08 +0100 [thread overview]
Message-ID: <20200203082908.GR10381@localhost> (raw)
In-Reply-To: <s5ha76085my.wl-tiwai@suse.de>
On Mon, Feb 03, 2020 at 08:57:41AM +0100, Takashi Iwai wrote:
> On Mon, 03 Feb 2020 00:28:16 +0100,
> edes wrote:
> >
> >
> > 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?
>
> I don't mind where to blacklist; we may add a similar quirk in
> USB-audio driver side, too.
I'm afraid it needs to be done in core since this info is needed while
parsing the descriptors.
Johan
next prev parent reply other threads:[~2020-02-03 8:29 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
2020-02-03 7:57 ` Takashi Iwai
2020-02-03 8:29 ` Johan Hovold [this message]
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=20200203082908.GR10381@localhost \
--to=johan@kernel.org \
--cc=edes@gmx.net \
--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;
as well as URLs for NNTP newsgroup(s).