From: Takashi Iwai <tiwai@suse.de>
To: Phil Willoughby <willerz@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, linux-sound@vger.kernel.org
Subject: Re: [PATCH 1/1] ALSA:usb-audio: Disable Arturia Audiofuse 16Rig
Date: Fri, 27 Mar 2026 14:43:10 +0100 [thread overview]
Message-ID: <87a4vtqtg1.wl-tiwai@suse.de> (raw)
In-Reply-To: <3610608.LZWGnKmheA@linux-workstation>
On Fri, 27 Mar 2026 14:22:01 +0100,
Phil Willoughby wrote:
>
> On Friday, 27 March 2026 12:20:59 Greenwich Mean Time you wrote:
> > On Thu, 19 Mar 2026 15:32:12 +0100,
> > Phil Willoughby wrote:
> > >
> > > There's an out of tree driver which works for some use-cases here:
> > >
> > > Link: https://github.com/WillerZ/arturia-af16rig-driver
> > >
> > > Signed-off-by: Phil Willoughby <willerz@gmail.com>
> > > Tested-by: Phil Willoughby <willerz@gmail.com>
> >
> > In general, we don't care much about the out-of-tree driver.
> > If it's upstreamed, of course we'd love to help. But this kind of
> > change is no-go.
>
> I'm happy to work on patches for an in-tree driver.
>
> It would need the patch chain you sent me that replaces the
> hardcoded channel max with MAX_CHANNELS and makes the channel mask
> 64-bits, because it has 34 channels.
If it's confirmed to work, I can submit and merge this beforehand.
> I'd also need to add one or two new quirk flags or device-id matching
> branches: which approach is preferred?
Well, it's hard to tell without comparing both changes...
thanks,
Takashi
prev parent reply other threads:[~2026-03-27 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 14:32 [PATCH 0/1] ALSA:usb-audio: Disable Arturia Audiofuse 16Rig Phil Willoughby
2026-03-19 14:32 ` [PATCH 1/1] " Phil Willoughby
2026-03-27 12:20 ` Takashi Iwai
2026-03-27 13:22 ` Phil Willoughby
2026-03-27 13:43 ` 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=87a4vtqtg1.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-sound@vger.kernel.org \
--cc=willerz@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