From: Takashi Iwai <tiwai@suse.de>
To: raoxu <raoxu@uniontech.com>
Cc: perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda: Fix cached processing coefficient verbs
Date: Tue, 07 Jul 2026 16:42:42 +0200 [thread overview]
Message-ID: <87v7aq6eu5.wl-tiwai@suse.de> (raw)
In-Reply-To: <DB9023BF2920BA99+20260707132419.1731342-1-raoxu@uniontech.com>
On Tue, 07 Jul 2026 15:24:19 +0200,
raoxu wrote:
>
> From: Xu Rao <raoxu@uniontech.com>
>
> Intel HD Audio defines Coefficient Index and Processing Coefficient as
> separate audio widget controls in the Audio Widget Verb Definitions:
> Coefficient Index selects the coefficient slot, while Processing
> Coefficient accesses the value at the selected slot.
>
> hda_reg_read_coef() selects the slot with AC_VERB_SET_COEF_INDEX, but
> then uses AC_VERB_GET_COEF_INDEX for the value read. That reads back the
> selected index instead of the coefficient value. hda_reg_write_coef()
> has the same issue and builds the value write from AC_VERB_GET_COEF_INDEX
> instead of AC_VERB_SET_PROC_COEF.
>
> This only affects the regmap coefficient cache path used by codecs that
> set codec->cache_coef. Direct coefficient helpers already use the normal
> SET_COEF_INDEX followed by GET_PROC_COEF or SET_PROC_COEF sequence, which
> is likely why this has not been noticed widely.
>
> Use AC_VERB_GET_PROC_COEF for cached coefficient reads and
> AC_VERB_SET_PROC_COEF for cached coefficient writes.
>
> Fixes: 40ba66a702b8 ("ALSA: hda - Add cache support for COEF read/write")
> Cc: stable@vger.kernel.org
> Signed-off-by: Xu Rao <raoxu@uniontech.com>
Ouch, this is a brown-paper-bag bug.
Applied now. Thanks!
Takashi
prev parent reply other threads:[~2026-07-07 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 13:24 [PATCH] ALSA: hda: Fix cached processing coefficient verbs raoxu
2026-07-07 14:42 ` 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=87v7aq6eu5.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=raoxu@uniontech.com \
--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