From: Neo Chang <YLCHANG2@nuvoton.com>
To: <broonie@kernel.org>
Cc: <lgirdwood@gmail.com>, <perex@perex.cz>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <linux-sound@vger.kernel.org>,
<devicetree@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<neo.chang70@gmail.com>, <kchsu0@nuvoton.com>,
<sjlin0@nuvoton.com>, "Neo Chang" <YLCHANG2@nuvoton.com>
Subject: [PATCH 2/2] ASoC: codecs: nau8360: Add default PEQ band number for DSP init
Date: Fri, 4 Sep 2026 10:44:56 +0800 [thread overview]
Message-ID: <20260904024456.193528-3-YLCHANG2@nuvoton.com> (raw)
In-Reply-To: <20260904024456.193528-1-YLCHANG2@nuvoton.com>
Set a default PEQ band number during DSP initialization to prevent
invalid state or uninitialized parameters before user configuration
is applied.
Signed-off-by: Neo Chang <YLCHANG2@nuvoton.com>
---
sound/soc/codecs/nau8360.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/sound/soc/codecs/nau8360.c b/sound/soc/codecs/nau8360.c
index b3cf207eea86..5a94e9a3072a 100644
--- a/sound/soc/codecs/nau8360.c
+++ b/sound/soc/codecs/nau8360.c
@@ -1602,6 +1602,8 @@ static void nau8360_coeff_set_def(struct nau8360 *nau8360)
i * NAU8360_TOT_BAND_COE_RANGE, 0x20);
}
nau8360_peq_mem_enable(regmap, false);
+ regmap_update_bits(regmap, NAU8360_R9D_PEQ_CTL, NAU8360_PEQ_BAND_MASK,
+ NAU8360_PEQ_BAND_8);
mutex_unlock(&nau8360->lock);
}
--
2.25.1
next prev parent reply other threads:[~2026-09-04 2:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 2:44 [PATCH 0/2] ASoC: codecs: nau8360: Add DSP fallback and PEQ band initialization Neo Chang
2026-09-04 2:44 ` [PATCH 1/2] ASoC: codecs: nau8360: Set DAC path to bypass mode when DSP firmware load fails Neo Chang
2026-09-04 2:55 ` sashiko-bot
2026-09-04 2:44 ` Neo Chang [this message]
2026-09-04 2:51 ` [PATCH 2/2] ASoC: codecs: nau8360: Add default PEQ band number for DSP init sashiko-bot
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=20260904024456.193528-3-YLCHANG2@nuvoton.com \
--to=ylchang2@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kchsu0@nuvoton.com \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=neo.chang70@gmail.com \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=sjlin0@nuvoton.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