From: Takashi Iwai <tiwai@suse.de>
To: Jegor van Opdorp <jegorvanopdorp@gmail.com>
Cc: linux-sound@vger.kernel.org, tiwai@suse.com, perex@perex.cz,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ALSA: usb-audio: add mixer support for Focusrite Forte
Date: Tue, 27 Jan 2026 10:00:23 +0100 [thread overview]
Message-ID: <87pl6v2zx4.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260127081541.219669-1-jegorvanopdorp@gmail.com>
On Tue, 27 Jan 2026 09:15:41 +0100,
Jegor van Opdorp wrote:
>
> Add mixer control support for the Focusrite Forte (USB ID 0x1235:0x8010),
> an older USB audio interface that predates the Scarlett 2nd generation.
>
> The Forte uses UAC2_CS_MEM (bRequest=0x03) for its input controls rather
> than the standard UAC2_CS_CUR (0x01) used by Scarlett devices. This patch
> adds Forte-specific control handlers that use the correct USB protocol.
>
> Features implemented:
> - Input source selection (Mic/Line/Inst) for both channels
> - High pass filter switch
> - 48V phantom power switch
> - Phase invert switch
> - Pad switch
> - Preamp gain control (0-42 range, ~0-75dB)
> - Matrix mixer controls (6 inputs x 4 outputs)
> - Output volume and mute controls
>
> The device is registered via mixer_quirks.c and uses the existing
> mixer_scarlett.c infrastructure with Forte-specific additions.
>
> Credit: This work builds on prior reverse-engineering by alastair-dm.
>
> Link: https://github.com/alastair-dm/forte-mixer/wiki
> Link: https://github.com/alastair-dm/forte-mixer
> Link: https://github.com/jopdorp/forte-mixer
> Signed-off-by: Jegor van Opdorp <jegorvanopdorp@gmail.com>
Thanks, applied now to for-next branch.
I noticed that I took your previous version mistakenly, so I dropped
it and reapplied the v2.
Takashi
prev parent reply other threads:[~2026-01-27 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 8:15 [PATCH v2] ALSA: usb-audio: add mixer support for Focusrite Forte Jegor van Opdorp
2026-01-27 9:00 ` 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=87pl6v2zx4.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=jegorvanopdorp@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--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