All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dicheng Wang <wangdicheng123@hotmail.com>
To: perex@perex.cz, tiwai@suse.com, sdoregor@sdore.me,
	hahnjo@hahnjo.de, wangdicheng@kylinos.cn,
	connerknoxpublic@gmail.com
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 -next] ALSA:usb-audio:add the information of KT0206 device driven by USB audio
Date: Wed,  7 Dec 2022 16:20:36 +0800	[thread overview]
Message-ID: <SG2PR02MB587849631CB96809CF90DBED8A1A9@SG2PR02MB5878.apcprd02.prod.outlook.com> (raw)

From: wangdicheng <wangdicheng@kylinos.cn>

Add relevant information to the quirks-table.h file.
The test passes and the sound source file plays normally.

Signed-off-by: wangdicheng <wangdicheng@kylinos.cn>
---
v3:add body information 

v2:use USB_DEVICE_VENDOR_SPEC() suggested by Takashi Iwai

 sound/usb/quirks-table.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/sound/usb/quirks-table.h b/sound/usb/quirks-table.h
index 874fcf245747..271884e35003 100644
--- a/sound/usb/quirks-table.h
+++ b/sound/usb/quirks-table.h
@@ -76,6 +76,8 @@
 { USB_DEVICE_VENDOR_SPEC(0x041e, 0x3f0a) },
 /* E-Mu 0204 USB */
 { USB_DEVICE_VENDOR_SPEC(0x041e, 0x3f19) },
+/* Ktmicro Usb_audio device */
+{ USB_DEVICE_VENDOR_SPEC(0x31b2, 0x0011) },
 
 /*
  * Creative Technology, Ltd Live! Cam Sync HD [VF0770]
-- 
2.25.1


             reply	other threads:[~2022-12-07  8:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-07  8:20 Dicheng Wang [this message]
2022-12-07 12:26 ` [PATCH v3 -next] ALSA:usb-audio:add the information of KT0206 device driven by USB audio Takashi Iwai
2022-12-07 12:26   ` Takashi Iwai
  -- strict thread matches above, loose matches on Subject: below --
2022-12-06 12:25 [PATCH v2 -next] ALSA:usb-audio:Add " Greg KH
2022-12-07  3:20 ` [PATCH v3 -next] ALSA:usb-audio:add " Dicheng Wang
2022-12-07  3:20   ` Dicheng Wang
2022-12-07  3:21   ` kernel test robot
2022-12-07  7:13   ` Greg KH
2022-12-07  7:13     ` Greg KH

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=SG2PR02MB587849631CB96809CF90DBED8A1A9@SG2PR02MB5878.apcprd02.prod.outlook.com \
    --to=wangdicheng123@hotmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=connerknoxpublic@gmail.com \
    --cc=hahnjo@hahnjo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=sdoregor@sdore.me \
    --cc=tiwai@suse.com \
    --cc=wangdicheng@kylinos.cn \
    /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.