From: Shengjiu Wang <shengjiu.wang@nxp.com>
To: shengjiu.wang@gmail.com, Xiubo.Lee@gmail.com, festevam@gmail.com,
nicoleotsuka@gmail.com, lgirdwood@gmail.com, broonie@kernel.org,
perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 00/11] ASoC: fsl: fix mixer-test failures
Date: Wed, 1 Apr 2026 17:42:15 +0800 [thread overview]
Message-ID: <20260401094226.2900532-1-shengjiu.wang@nxp.com> (raw)
Fix mixer-test failures. Mostly the issues are that event is not
generated in put operation.
changes in v2:
- add back event notification in patch 11/11
Shengjiu Wang (11):
ASoC: fsl_micfil: Add access property for "VAD Detected"
ASoC: fsl_micfil: Fix event generation in hwvad_put_enable()
ASoC: fsl_micfil: Fix event generation in hwvad_put_init_mode()
ASoC: fsl_micfil: Fix event generation in micfil_range_set()
ASoC: fsl_micfil: Fix event generation in
micfil_put_dc_remover_state()
ASoC: fsl_micfil: Fix event generation in micfil_quality_set()
ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_arc_mode_put()
ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_mode_put()
ASoC: fsl_easrc: Check the variable range in
fsl_easrc_iec958_put_bits()
ASoC: fsl_easrc: Fix value type in fsl_easrc_iec958_get_bits()
ASoC: fsl_easrc: Change the type for iec958 channel status controls
sound/soc/fsl/fsl_easrc.c | 123 ++++++++++++++++++++++++++-----------
sound/soc/fsl/fsl_micfil.c | 72 +++++++++++++++++++---
sound/soc/fsl/fsl_xcvr.c | 22 +++++--
3 files changed, 168 insertions(+), 49 deletions(-)
--
2.34.1
next reply other threads:[~2026-04-01 9:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 9:42 Shengjiu Wang [this message]
2026-04-01 9:42 ` [PATCH v2 01/11] ASoC: fsl_micfil: Add access property for "VAD Detected" Shengjiu Wang
2026-04-01 9:42 ` [PATCH v2 02/11] ASoC: fsl_micfil: Fix event generation in hwvad_put_enable() Shengjiu Wang
2026-04-01 9:42 ` [PATCH v2 03/11] ASoC: fsl_micfil: Fix event generation in hwvad_put_init_mode() Shengjiu Wang
2026-04-01 9:42 ` [PATCH v2 04/11] ASoC: fsl_micfil: Fix event generation in micfil_range_set() Shengjiu Wang
2026-04-01 9:42 ` [PATCH v2 05/11] ASoC: fsl_micfil: Fix event generation in micfil_put_dc_remover_state() Shengjiu Wang
2026-04-01 9:42 ` [PATCH v2 06/11] ASoC: fsl_micfil: Fix event generation in micfil_quality_set() Shengjiu Wang
2026-04-01 9:42 ` [PATCH v2 07/11] ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_arc_mode_put() Shengjiu Wang
2026-04-01 9:42 ` [PATCH v2 08/11] ASoC: fsl_xcvr: Fix event generation in fsl_xcvr_mode_put() Shengjiu Wang
2026-04-01 9:42 ` [PATCH v2 09/11] ASoC: fsl_easrc: Check the variable range in fsl_easrc_iec958_put_bits() Shengjiu Wang
2026-04-01 9:42 ` [PATCH v2 10/11] ASoC: fsl_easrc: Fix value type in fsl_easrc_iec958_get_bits() Shengjiu Wang
2026-04-01 9:42 ` [PATCH v2 11/11] ASoC: fsl_easrc: Change the type for iec958 channel status controls Shengjiu Wang
2026-04-01 17:24 ` [PATCH v2 00/11] ASoC: fsl: fix mixer-test failures Mark Brown
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=20260401094226.2900532-1-shengjiu.wang@nxp.com \
--to=shengjiu.wang@nxp.com \
--cc=Xiubo.Lee@gmail.com \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=shengjiu.wang@gmail.com \
--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