From: Takashi Iwai <tiwai@suse.de>
To: Hui Wang <hui.wang@canonical.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock
Date: Tue, 27 Nov 2018 12:23:43 +0100 [thread overview]
Message-ID: <s5hh8g2yda8.wl-tiwai@suse.de> (raw)
In-Reply-To: <20181127013332.7494-1-hui.wang@canonical.com>
On Tue, 27 Nov 2018 02:33:32 +0100,
Hui Wang wrote:
>
> Like the Dell WD15 Dock, the WD19 Dock (0bda:402e) doens't provide
> useful string for the vendor and product names too, and WD19 has a
> headset Jack and a Speaker out Jack. In order to support UCM for this
> Dock in the alsa-lib, here we add profile_name too.
>
> Signed-off-by: Hui Wang <hui.wang@canonical.com>
Looking at the UCM addition, it's same as WD15 but just a different
name? What you put "Speaker" was "Line Out" on WD15, but it was meant
to be same. Line Out was chosen just because of convention.
I'm OK to add a new one, but keeping "Dell-WD15-Dock" makes the new
kernel working even without UCM profile update.
thanks,
Takashi
> ---
> sound/usb/quirks-table.h | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/sound/usb/quirks-table.h b/sound/usb/quirks-table.h
> index 849953e5775c..4c10015cc0ca 100644
> --- a/sound/usb/quirks-table.h
> +++ b/sound/usb/quirks-table.h
> @@ -3382,5 +3382,15 @@ AU0828_DEVICE(0x2040, 0x7270, "Hauppauge", "HVR-950Q"),
> .ifnum = QUIRK_NO_INTERFACE
> }
> },
> +/* Dell WD19 Dock */
> +{
> + USB_DEVICE(0x0bda, 0x402e),
> + .driver_info = (unsigned long) & (const struct snd_usb_audio_quirk) {
> + .vendor_name = "Dell",
> + .product_name = "WD19 Dock",
> + .profile_name = "Dell-WD19-Dock",
> + .ifnum = QUIRK_NO_INTERFACE
> + }
> +},
>
> #undef USB_DEVICE_VENDOR_SPEC
> --
> 2.17.1
>
next prev parent reply other threads:[~2018-11-27 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 1:33 [PATCH] ALSA: usb-audio: Add vendor and product name for Dell WD19 Dock Hui Wang
2018-11-27 11:23 ` Takashi Iwai [this message]
2018-11-28 1:14 ` Hui Wang
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=s5hh8g2yda8.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=hui.wang@canonical.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