Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Geoffrey D. Bennett" <g@b4.vu>
To: Takashi Iwai <tiwai@suse.de>
Cc: Takashi Iwai <tiwai@suse.com>, linux-sound@vger.kernel.org
Subject: [PATCH 0/2] ALSA: Add driver for big Scarlett 4th Gen interfaces
Date: Thu, 26 Dec 2024 07:53:06 +1030	[thread overview]
Message-ID: <cover.1735159288.git.g@b4.vu> (raw)

Hi Takashi,

Merry Christmas!

This patch series introduces a new Focusrite Control Protocol (FCP)
driver that provides equivalent functionality to the existing
Scarlett2 driver, but splits the implementation between a minimal
kernel driver and a user-space component. My initial user-space
implementation supports the new Scarlett 4th Gen 16i16, 18i16, and
18i20 interfaces, but the new FCP kernel driver can be used with any
device supported by the Scarlett2 driver (as an opt-in).

With these new interfaces, I started out by trying to extend the
existing Scarlett2 driver but found that that wasn't practical. The
control locations (struct scarlett2_config offset field) have
previously varied between firmware versions (which is why I added the
"Minimum Firmware Version" requirement for previous 4th Gen and
Vocaster devices), and the situation was worse with the new 4th Gen
devices, with every new firmware version moving the controls.

While the device provides a map indicating control locations,
implementing the required JSON parsing in the kernel isn't feasible,
necessitating a user-space implementation.

The new approach in the FCP driver significantly improves both
maintainability and paves the way for future enhancements:

Firstly, the kernel component of the FCP driver is <10% the size of
the Scarlett2 driver, with the obvious maintainability advantages;
cloc reports:

File                            blank     comment        code
sound/usb/mixer_scarlett2.c      1765         852        7152
sound/usb/fcp.c                   174          64         645

Secondly, changes that aren't feasible to implement in the kernel due
to backward compatibility constraints will be able to be implemented
in user-space, with end-users easily able to choose an older version
of the controls if needed. For example:

1) The largest interface has >500 ALSA controls just for the matrix
mixer (one control for each entry in the N×M matrix). This would be
better done as N controls with M values each, especially since the
device supports writing a row (all input gains for one mixer output)
at a time.

2) Similarly, the mux table entries have a control per entry, but
they're all written at once, so it would be better to have a single
ALSA control for the whole mux table.

3) The interfaces have 3 independent mux tables (one per sample rate
48kHz, 96kHz, 192kHz), but supporting them isn't feasible in Scarlett2
due to backward compatibility constraints.

4) Users of the Scarlett2 driver frequently request higher-level
controls like stereo-linking, pan, mute, and solo. These would be very
challenging to implement in the kernel while maintaining backward
compatibility to the existing controls, but again, it's easy to have
configurable controls in user-space.

I did consider the alternative of a small user-space helper that just
reads the map (this is the direction I was heading with my previous
commit 9930c26 ALSA: scarlett2: Add support for device map retrieval)
and uploads the offsets to the driver, but this would add even more
complexity to the driver while gaining none of the possible benefits
of a user-space implementation. Since user-space implementation is
unavoidable, moving as much functionality there as possible provides
the cleanest and most maintainable solution.

Hence, I present for your consideration the following patches:

1) The new FCP driver implementation, handling only the essential
kernel-space components (base protocol and level meter)

2) An option enabling Scarlett2-supported devices to use the FCP
driver, providing an opt-in migration path forward

The accompanying user-space implementation is available at:
https://github.com/geoffreybennett/fcp-support

Thanks,
Geoffrey.

Geoffrey D. Bennett (2):
  ALSA: FCP: Add Focusrite Control Protocol driver
  ALSA: scarlett2: Add device_setup option to use FCP driver

 MAINTAINERS                 |  10 +-
 include/uapi/sound/fcp.h    |  59 +++
 sound/usb/Makefile          |   1 +
 sound/usb/fcp.c             | 883 ++++++++++++++++++++++++++++++++++++
 sound/usb/fcp.h             |   7 +
 sound/usb/mixer_quirks.c    |   7 +
 sound/usb/mixer_scarlett2.c |   8 +
 7 files changed, 971 insertions(+), 4 deletions(-)
 create mode 100644 include/uapi/sound/fcp.h
 create mode 100644 sound/usb/fcp.c
 create mode 100644 sound/usb/fcp.h

-- 
2.45.0


             reply	other threads:[~2024-12-25 21:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25 21:23 Geoffrey D. Bennett [this message]
2024-12-25 21:23 ` [PATCH 1/2] ALSA: FCP: Add Focusrite Control Protocol driver Geoffrey D. Bennett
2024-12-29  9:01   ` Takashi Iwai
2024-12-25 21:23 ` [PATCH 2/2] ALSA: scarlett2: Add device_setup option to use FCP driver Geoffrey D. Bennett
2024-12-29  8:41 ` [PATCH 0/2] ALSA: Add driver for big Scarlett 4th Gen interfaces 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=cover.1735159288.git.g@b4.vu \
    --to=g@b4.vu \
    --cc=linux-sound@vger.kernel.org \
    --cc=tiwai@suse.com \
    --cc=tiwai@suse.de \
    /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