Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Geoffrey D. Bennett" <g@b4.vu>
Cc: Hin-Tak Leung <htl10@users.sourceforge.net>,
	alsa-devel@alsa-project.org,
	Vladimir Sadovnikov <sadko4u@gmail.com>
Subject: Re: [PATCH 0/2] ALSA: scarlett2: Add "Standalone" switch
Date: Tue, 08 Mar 2022 10:06:29 +0100	[thread overview]
Message-ID: <s5hy21kn78q.wl-tiwai@suse.de> (raw)
In-Reply-To: <cover.1646578164.git.g@b4.vu>

On Sun, 06 Mar 2022 16:20:40 +0100,
Geoffrey D. Bennett wrote:
> 
> Hi Takashi,
> 
> I discovered an internal "standalone" switch on all the Scarlett Gen
> 2/3 interfaces with internal mixers. After enabling this switch, the
> interface will act as a standalone mixer (according to its previous
> configuration) when not connected to a USB host. The interfaces come
> from the factory with the switch off, and the vendor driver enables it
> without question. This patch adds a new ALSA control to set the switch
> on or off.
> 
> This is the first configuration item that is common between the Gen 2
> and 3 interfaces but with a different offset, so the patch is in two
> parts. The first patch allows for the same configuration item to have
> a different offset between Gen 2/3 and the second patch adds the new
> switch.
> 
> Regards,
> Geoffrey.
> 
> Geoffrey D. Bennett (2):
>   ALSA: scarlett2: Split scarlett2_config_items[] into 3 sections
>   ALSA: scarlett2: Add support for the internal "standalone" switch

Thanks, applied both patches now.


Takashi

      parent reply	other threads:[~2022-03-08  9:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-06 15:20 [PATCH 0/2] ALSA: scarlett2: Add "Standalone" switch Geoffrey D. Bennett
2022-03-06 15:21 ` [PATCH 1/2] ALSA: scarlett2: Split scarlett2_config_items[] into 3 sections Geoffrey D. Bennett
2022-03-06 15:21 ` [PATCH 2/2] ALSA: scarlett2: Add support for the internal "standalone" switch Geoffrey D. Bennett
2022-03-08  9:06 ` Takashi Iwai [this message]

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=s5hy21kn78q.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=g@b4.vu \
    --cc=htl10@users.sourceforge.net \
    --cc=sadko4u@gmail.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