Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Faaris Ansari <faaris.ansari@gmail.com>
Cc: "Takashi Iwai" <tiwai@suse.de>,
	"Faaris Ansari" <faarisansari@googlemail.com>,
	"Sasha Levin" <sashal@kernel.org>,
	stable@vger.kernel.org, regressions@lists.linux.dev,
	linux-sound@vger.kernel.org,
	"Cássio Gabriel" <cassiogabrielcontato@gmail.com>,
	"Takashi Iwai" <tiwai@suse.com>,
	"Jaroslav Kysela" <perex@perex.cz>
Subject: Re: [REGRESSION] Audient EVO4 hardware volume control now requires quirk
Date: Tue, 29 Sep 2026 16:28:59 +0200	[thread overview]
Message-ID: <87wls4yvv8.wl-tiwai@suse.de> (raw)
In-Reply-To: <0e1a1284-7069-4c46-9f35-57c10c129883@gmail.com>

On Tue, 29 Sep 2026 16:24:24 +0200,
Faaris Ansari wrote:
> 
> Thanks Takashi and Sasha,
> 
> 
> > Faaris, please let us know if this (or previous) one actually works
> > for you.  Once after confirmation, I'll submit the proper patch for
> > upstream.
> 
> I tested your latest patch where you removed the quirk for the iD14
> alone, and instead set it for all Audient devices.
> 
> I can confirm that this has indeed fixed the problem, and I can now
> correctly control my hardware volume without problems, thank you!
> 
> 
> > ... or if you have a chance to test Christian's patch set and verify
> > whether the problem is fixed there, we can avoid other changes:
> >    https://lore.kernel.org/20260919151840.24371-1-arc@gmx.li
> I tested Christian's patch alone, without any other changes. The
> problem still occurred with those patches.
> 
> This was also noted by Christian:
> 
> > As a matter of fact, I made a similar
> > observation to yours when testing the patch set on the 'sound' kernel tree
> > and the (very sporadic) issue did not disappear after applying the
> > patches.
> And further discussion below:
> 
> https://lore.kernel.org/all/CANBVYRAr8iFGFDgdTcDXuQyXt5M4TddZetsG9o1wbFao03R0yw@mail.gmail.com/
> 
> 
> However, using both patches together (as well as a small patch for
> alsa-ucm-conf) has made my interface work very well - I'm very happy
> with these changes :)
> 
> 
> Thank you for your work, Sasha, Takashi, and Christian,
> 
> Faaris

Thanks for clarification.  Then we need a fix like mine in anyway.
I'm going to submit the proper patch.


Takashi

  reply	other threads:[~2026-09-29 14:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-26 13:03 [REGRESSION] Audient EVO4 hardware volume control now requires quirk Faaris Ansari
2026-09-27 14:26 ` Sasha Levin
2026-09-27 22:50   ` Faaris Ansari
2026-09-28 16:46     ` Sasha Levin
2026-09-28 16:53       ` Faaris Ansari
2026-09-28 22:39         ` Sasha Levin
2026-09-29  5:58           ` Takashi Iwai
2026-09-29 12:38             ` Takashi Iwai
2026-09-29 13:14               ` Takashi Iwai
2026-09-29 14:24                 ` Faaris Ansari
2026-09-29 14:28                   ` Takashi Iwai [this message]
2026-09-29 19:46                     ` Christian Ruppert
2026-10-02 14:19                     ` Sasha Levin
2026-10-02 14:37                       ` Takashi Iwai
2026-10-02 21:10                         ` Sasha Levin
2026-10-03  1:30                           ` Sasha Levin

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=87wls4yvv8.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=cassiogabrielcontato@gmail.com \
    --cc=faaris.ansari@gmail.com \
    --cc=faarisansari@googlemail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --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