From: Pengpeng Hou <hppiscas@163.com>
To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: Pengpeng Hou <hppiscas@163.com>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>,
David Yang <yangxiaohua@everest-semi.com>,
Zhu Ning <zhuning0077@gmail.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhang Yi <zhangyi@everest-semi.com>,
Nick Li <nick.li@foursemi.com>
Subject: [PATCH 0/4] ASoC: report additional component restore failures
Date: Sun, 6 Sep 2026 11:42:13 +0800 [thread overview]
Message-ID: <20260906034217.85696-1-hppiscas@163.com> (raw)
The three Everest resume callbacks ignore status reads before branching on
their output and then discard later restore failures. The FS210x helper marks
its cache dirty but publishes is_inited even when replay fails.
Check the fallible operations that delimit each restore transaction and
return before publishing dependent IRQ or software state. Commit
951af101c730 ("ASoC: report component resume callback errors") reports these
callback results while retaining ASoC's best-effort deferred resume behavior.
The issues were found by our static-analysis tool and manually reviewed.
Pengpeng Hou (4):
ASoC: es8326: report resume restore errors
ASoC: es8375: report resume restore errors
ASoC: es8389: report resume restore errors
ASoC: fs210x: report register restore errors
sound/soc/codecs/es8326.c | 20 +++++++++++++++-----
sound/soc/codecs/es8375.c | 18 +++++++++++-------
sound/soc/codecs/es8389.c | 20 ++++++++++++++------
sound/soc/codecs/fs210x.c | 5 +++--
4 files changed, 43 insertions(+), 20 deletions(-)
--
2.50.1 (Apple Git-155)
reply other threads:[~2026-09-06 3:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260906034217.85696-1-hppiscas@163.com \
--to=hppiscas@163.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=nick.li@foursemi.com \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=yangxiaohua@everest-semi.com \
--cc=zhangyi@everest-semi.com \
--cc=zhuning0077@gmail.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