mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Faaris Ansari <faaris.ansari@gmail.com>
To: arc@gmx.li
Cc: drabik.p@gmail.com, linux-kernel@vger.kernel.org,
	linux-sound@vger.kernel.org, mrwillporter@gmail.com,
	neil@androos.io, perex@perex.cz, tiwai@suse.com
Subject: Re: [PATCH 0/3] Add Audient EVO4 support
Date: Fri, 25 Sep 2026 11:18:33 +0100	[thread overview]
Message-ID: <92b1eece-9dc7-4b33-9ec5-fc94300038f1@gmail.com> (raw)
In-Reply-To: <20260919151840.24371-1-arc@gmx.li>

Thanks for your work on this - there is currently a regression on the 
latest kernel versions (7.2 onwards, as well as LTS kernels 6.12 and 
6.18). Trying to set the volume in software like wpctl, or pwvucontrol 
causes the software volume to be pulled down with it - I think it's 
something to do with "sticky mixers", not completely sure.

I worked through troubleshooting it here as I originally thought it was 
a wireplumber issue: 
https://gitlab.freedesktop.org/pipewire/wireplumber/-/work_items/1022

This patch should hopefully solve that, and avoid the usage of external 
kernel modules like https://github.com/vanzaho/audient-evo-py (which 
you've based your work from)

I'm not exactly sure how the process with kernel stuff works, but 
considering a regression on current mainline as well as LTS branches for 
this device - is there some chance of fast tracking the merge of these 
patches?

Thanks, Faaris



  parent reply	other threads:[~2026-09-25 10:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19 15:18 Christian Ruppert
2026-09-19 15:18 ` [PATCH 1/3] Fix Audient EVO4 master playback control name Christian Ruppert
2026-09-19 15:18 ` [PATCH 2/3] Add Audient EVO4 mixer quirks Christian Ruppert
2026-09-19 15:18 ` [PATCH 3/3] Add Kconfig option for " Christian Ruppert
2026-09-25 10:18 ` Faaris Ansari [this message]
2026-09-27 17:12   ` [PATCH 0/3] Add Audient EVO4 support Christian Ruppert
2026-09-27 17:38     ` Faaris Ansari
2026-09-29 13:21 ` Takashi Iwai
2026-09-29 19:49   ` Christian Ruppert

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=92b1eece-9dc7-4b33-9ec5-fc94300038f1@gmail.com \
    --to=faaris.ansari@gmail.com \
    --cc=arc@gmx.li \
    --cc=drabik.p@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=mrwillporter@gmail.com \
    --cc=neil@androos.io \
    --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
all inboxes | Powered by JetHome®