From: Takashi Iwai <tiwai@suse.de>
To: Joshua Pius <joshuapius@chromium.org>
Cc: alsa-devel@alsa-project.org, Joshua Pius <joshuapius@google.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
"Steven 'Steve' Kendall" <skend@chromium.org>,
Karol Kosik <k.kosik@outlook.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: usb-audio: Add logitech Audio profile quirk
Date: Sun, 08 Sep 2024 09:48:17 +0200 [thread overview]
Message-ID: <878qw2d1ry.wl-tiwai@suse.de> (raw)
In-Reply-To: <20240906211445.3924724-1-joshuapius@google.com>
On Fri, 06 Sep 2024 23:14:38 +0200,
Joshua Pius wrote:
>
> Specify shortnames for the following Logitech Devices: Rally bar, Rally
> bar mini, Tap, MeetUp and Huddle.
>
> Signed-off-by: Joshua Pius <joshuapius@google.com>
Is this change needed only for UCM profiles? UCM v2 should be able to
handle better to identify models, and such short name updates aren't
needed for them.
OTOH, I don't mind much to take this kind of small harmless changes
(unless it happens too frequently). So I'll likely take this, but
just for verifying the situation.
thanks,
Takashi
> ---
> sound/usb/card.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/sound/usb/card.c b/sound/usb/card.c
> index 778de9244f1e..9c411b82a218 100644
> --- a/sound/usb/card.c
> +++ b/sound/usb/card.c
> @@ -384,6 +384,12 @@ static const struct usb_audio_device_name usb_audio_names[] = {
> /* Creative/Toshiba Multimedia Center SB-0500 */
> DEVICE_NAME(0x041e, 0x3048, "Toshiba", "SB-0500"),
>
> + /* Logitech Audio Devices */
> + DEVICE_NAME(0x046d, 0x0867, "Logitech, Inc.", "Logi-MeetUp"),
> + DEVICE_NAME(0x046d, 0x0874, "Logitech, Inc.", "Logi-Tap-Audio"),
> + DEVICE_NAME(0x046d, 0x087c, "Logitech, Inc.", "Logi-Huddle"),
> + DEVICE_NAME(0x046d, 0x0898, "Logitech, Inc.", "Logi-RB-Audio"),
> + DEVICE_NAME(0x046d, 0x08d2, "Logitech, Inc.", "Logi-RBM-Audio"),
> DEVICE_NAME(0x046d, 0x0990, "Logitech, Inc.", "QuickCam Pro 9000"),
>
> DEVICE_NAME(0x05e1, 0x0408, "Syntek", "STK1160"),
> --
> 2.46.0.598.g6f2099f65c-goog
>
next prev parent reply other threads:[~2024-09-08 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 21:14 [PATCH] ALSA: usb-audio: Add logitech Audio profile quirk Joshua Pius
2024-09-08 7:48 ` Takashi Iwai [this message]
2024-09-09 2:03 ` Joshua Pius
2024-09-10 8:26 ` Takashi Iwai
2024-09-11 19:27 ` Joshua Pius
2024-09-12 7:23 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2024-09-12 15:26 Joshua Pius
2024-09-12 16:01 ` Takashi Iwai
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=878qw2d1ry.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=joshuapius@chromium.org \
--cc=joshuapius@google.com \
--cc=k.kosik@outlook.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=skend@chromium.org \
--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