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 v2 0/2] ASoC: codecs: nau8360: Add DSP fallback and PEQ band initialization
Date: Fri, 4 Sep 2026 14:00:33 +0800 [thread overview]
Message-ID: <20260904060035.196399-1-YLCHANG2@nuvoton.com> (raw)
This patch series adds a fallback mechanism for the NAU8360 DSP during
firmware load failure and ensures proper initialization for PEQ bands.
It includes the following changes:
- Fallback to bypass mode automatically when DSP firmware fails to load,
ensuring basic audio playback remains functional.
- Set a default PEQ band number during DSP initialization to prevent
invalid state or uninitialized parameters before user configuration
is applied.
Changes in v2:
- Use snd_soc_component_update_bits() to prevent register overwriting.
(Reported by Sashiko AI)
- Fix missing bit shift for default PEQ band. (Reported by Sashiko AI)
Neo Chang (2):
ASoC: codecs: nau8360: Set DAC path to bypass mode when DSP firmware
load fails
ASoC: codecs: nau8360: Add default PEQ band number for DSP init
sound/soc/codecs/nau8360.c | 4 ++++
1 file changed, 4 insertions(+)
--
2.25.1
next reply other threads:[~2026-09-04 6:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 6:00 Neo Chang [this message]
2026-09-04 6:00 ` [PATCH v2 1/2] ASoC: codecs: nau8360: Set DAC path to bypass mode when DSP firmware load fails Neo Chang
2026-09-04 6:16 ` sashiko-bot
2026-09-04 17:47 ` Mark Brown
2026-09-04 6:00 ` [PATCH v2 2/2] ASoC: codecs: nau8360: Add default PEQ band number for DSP init Neo Chang
2026-09-04 17:48 ` (subset) [PATCH v2 0/2] ASoC: codecs: nau8360: Add DSP fallback and PEQ band initialization 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=20260904060035.196399-1-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