All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Reza Jahanbakhshi <reza.jahanbakhshi@gmail.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	Takashi Iwai <tiwai@suse.com>,
	Johannes Schickel <lordhoto@gmail.com>,
	Timo Gurr <timo.gurr@gmail.com>
Subject: Re: [PATCH] ALSA: usb-audio: add mapping for new Corsair Virtuoso SE
Date: Sat, 05 Mar 2022 09:27:46 +0100	[thread overview]
Message-ID: <s5hee3gregt.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220304212303.195949-1-reza.jahanbakhshi@gmail.com>

On Fri, 04 Mar 2022 22:23:02 +0100,
Reza Jahanbakhshi wrote:
> 
> New device id for Corsair Virtuoso SE RGB Wireless that currently is not
> in the mixer_map. This entry in the mixer_map is necessary in order to
> label its mixer appropriately and allow userspace to pick the correct
> volume controls. For instance, my own Corsair Virtuoso SE RGB Wireless
> headset has this new ID and consequently, the sidetone and volume are not
>  working correctly without this change.
> > sudo lsusb -v | grep -i corsair
> Bus 007 Device 011: ID 1b1c:0a40 Corsair CORSAIR VIRTUOSO SE Wireless Gam
>   idVendor           0x1b1c Corsair
>   iManufacturer           1 Corsair
>   iProduct                2 CORSAIR VIRTUOSO SE Wireless Gaming Headset
> 
> Signed-off-by: Reza Jahanbakhshi <reza.jahanbakhshi@gmail.com>

Thanks, applied now with Cc-to-stable.


Takashi

WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Reza Jahanbakhshi <reza.jahanbakhshi@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	Johannes Schickel <lordhoto@gmail.com>,
	Timo Gurr <timo.gurr@gmail.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: usb-audio: add mapping for new Corsair Virtuoso SE
Date: Sat, 05 Mar 2022 09:27:46 +0100	[thread overview]
Message-ID: <s5hee3gregt.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220304212303.195949-1-reza.jahanbakhshi@gmail.com>

On Fri, 04 Mar 2022 22:23:02 +0100,
Reza Jahanbakhshi wrote:
> 
> New device id for Corsair Virtuoso SE RGB Wireless that currently is not
> in the mixer_map. This entry in the mixer_map is necessary in order to
> label its mixer appropriately and allow userspace to pick the correct
> volume controls. For instance, my own Corsair Virtuoso SE RGB Wireless
> headset has this new ID and consequently, the sidetone and volume are not
>  working correctly without this change.
> > sudo lsusb -v | grep -i corsair
> Bus 007 Device 011: ID 1b1c:0a40 Corsair CORSAIR VIRTUOSO SE Wireless Gam
>   idVendor           0x1b1c Corsair
>   iManufacturer           1 Corsair
>   iProduct                2 CORSAIR VIRTUOSO SE Wireless Gaming Headset
> 
> Signed-off-by: Reza Jahanbakhshi <reza.jahanbakhshi@gmail.com>

Thanks, applied now with Cc-to-stable.


Takashi

  reply	other threads:[~2022-03-05  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 21:23 [PATCH] ALSA: usb-audio: add mapping for new Corsair Virtuoso SE Reza Jahanbakhshi
2022-03-04 21:23 ` Reza Jahanbakhshi
2022-03-05  8:27 ` Takashi Iwai [this message]
2022-03-05  8:27   ` 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=s5hee3gregt.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lordhoto@gmail.com \
    --cc=reza.jahanbakhshi@gmail.com \
    --cc=timo.gurr@gmail.com \
    --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 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.