From: Rong Zhang <i@rong.moe>
To: 胡连勤 <hulianqin@vivo.com>, "perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>
Cc: "linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: usb-audio: Add iface reset and delay quirk for JKY Technology Q2A
Date: Fri, 24 Jul 2026 19:08:38 +0800 [thread overview]
Message-ID: <2cb27fb80f6fbdbd3b72138ce2d33c878e4e8049.camel@rong.moe> (raw)
In-Reply-To: <TYUPR06MB6217BD7BF1AE9B308295FFFCD2CF2@TYUPR06MB6217.apcprd06.prod.outlook.com>
Hi Takashi, Lianqin,
On Fri, 2026-07-24 at 08:29 +0000, 胡连勤 wrote:
> Setting up the interface when suspended/resuming fails on this card.
> Adding a reset and delay quirk will eliminate this problem.
>
> Note: This device misuses the Apple VID (0x05ac) & PID (0x110b).
The device's VID conflicts with Apple's, but there is no PID conflict,
right?
If a manufacturer uses other's VID, it's a VID conflict. The device
falls into this category.
If the manufacturer uses the same PID among different products, it's a
PID conflict. I don't think it's the case of the device, unless JKY
Technology reuses PID 0x110b for products other than Q2A.
>
> usb 1-1: New USB device found, idVendor=05ac, idProduct=110b
> usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-1: Product: Q2A
> usb 1-1: Manufacturer: JKY Technology
> usb 1-1: SerialNumber: 330270D2251225
>
> Signed-off-by: Lianqin Hu <hulianqin@vivo.com>
> ---
> sound/usb/quirks.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/sound/usb/quirks.c b/sound/usb/quirks.c
> index 0de7c9d94259..ad2ce384e32d 100644
> --- a/sound/usb/quirks.c
> +++ b/sound/usb/quirks.c
> @@ -2200,6 +2200,8 @@ struct usb_audio_quirk_flags_table {
>
> static const struct usb_audio_quirk_flags_table quirk_flags_table[] = {
> /* Device and string descriptor matches */
> + DEVICE_STRING_FLG(0x05ac, 0x110b, "JKY Technology", "Q2A", /* JKY Technology Q2A */
Hence, I don't think it's necessary to match "Q2A" here.
Meanwhile, in any case, the comment should describe the VID/PID conflict
instead of repeating the string descriptor(s) being matched, and the
strings should break into another line.
See how commit b13031ca112a ("ALSA: usb-audio: Deconflict VID between
Focusrite Novation & MV-SILICON") describe the conflict and arrange
lines.
> + QUIRK_FLAG_FORCE_IFACE_RESET | QUIRK_FLAG_IFACE_DELAY),
Bad indent.
This is the first DEVICE_STRING_FLG() item, so please don't set a bad
example. I would prefer:
DEVICE_STRING_FLG(0x05ac, 0x110b, /* VID conflicts with Apple */
"JKY Technology", NULL /* Q2A */,
QUIRK_FLAG_FORCE_IFACE_RESET | QUIRK_FLAG_IFACE_DELAY),
Thanks,
Rong
>
> /* Device matches */
> DEVICE_FLG(0x001f, 0x0b21, /* AB13X USB Audio */
> --
> 2.39.0
next prev parent reply other threads:[~2026-07-24 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 8:29 胡连勤
2026-07-24 9:08 ` Takashi Iwai
2026-07-24 11:08 ` Rong Zhang [this message]
2026-07-24 11:30 ` Takashi Iwai
2026-07-24 11:56 ` 答复: " 胡连勤
2026-07-24 11:41 ` 胡连勤
2026-07-24 12:02 ` Rong Zhang
2026-07-24 12:11 ` 答复: " 胡连勤
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=2cb27fb80f6fbdbd3b72138ce2d33c878e4e8049.camel@rong.moe \
--to=i@rong.moe \
--cc=hulianqin@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@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
all inboxes | Powered by JetHome®