mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>, Seven Lee <wtli@nuvoton.com>,
	linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	John Hsu <supercraig0719@gmail.com>,
	"Fang, Yang A" <yang.a.fang@intel.com>,
	Yong Zhi <yong.zhi@intel.com>,
	Oder Chiou <oder_chiou@realtek.com>,
	Jack Yu <jack.yu@realtek.com>, Bard Liao <bardliao@realtek.com>,
	John Lin <john.lin@realtek.com>,
	Derek Fang <derek.fang@realtek.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	patches@opensource.cirrus.com,
	Stephen Warren <swarren@nvidia.com>,
	Charles Keepax <ckeepax@opensource.cirrus.com>
Subject: [PATCH v2 0/9] ASoC: stop dependent resume work after restore failures
Date: Wed, 14 Oct 2026 11:24:43 +0800	[thread overview]
Message-ID: <20261014032452.13456-1-hppiscas@163.com> (raw)

This revision addresses Mark's cache-mode concern and Charles's WM8978
bias rollback question. It also accounts for the next suspend after a
failed resume: the ASoC wrapper reports the callback error but marks the
component resumed, so leaving an IRQ disabled needs driver-local ownership
tracking to avoid disabling it a second time in the next suspend.

All nine changes retain best-effort card resume. They do not add framework
rollback or automatic retries. The RT5682 SoundWire branch and RT5677
retained VAD path keep their existing behavior. RT5640 handles both IRQ
producers of jack work and clears ownership when either IRQ is freed.
RT5677 also propagates normal-mode transport write errors and remembers
pending restoration across later changes to the requested VAD mode.

These issues were found by our static-analysis tool and manually reviewed.
The code and descriptions were prepared with gpt 5 assistance; the patches
carry the corresponding Assisted-by trailers.

Changes since v1:
- restore cache-only mode and preserve dirty state on replay errors
- avoid repeated suspend-owned IRQ disables after failed resume
- return WM8978 bias to OFF on failure, without claiming hardware rollback
  is guaranteed when the bias callback itself ignores register errors
- clear WM8978 PLL power as system suspend does
- quiesce both RT5640 jack IRQs and reject fresh setup while unrestored
- fix RT5677's normal-mode write error propagation and pending-restore state
- preserve the per-driver power, SoundWire and DSP VAD distinctions
- resend all members as one series rather than separate unthreaded posts

Previous series:
https://lore.kernel.org/all/20260906034321.86080-1-hppiscas@163.com/

Base: 8ef28aef33f2d5da6959ad6b579ec3cfccc009f6 (sound/for-next)

1. ASoC: nau8821: restore safe state after resume errors
2. ASoC: nau8824: restore safe state after resume errors
3. ASoC: nau8825: restore safe state after resume errors
4. ASoC: rt5663: restore safe state after resume errors
5. ASoC: rt5682s: restore safe state after resume errors
6. ASoC: rt5682: restore safe state after resume errors
7. ASoC: wm8978: restore safe state after resume errors
8. ASoC: rt5640: restore safe state after resume errors
9. ASoC: rt5677: restore safe state after resume errors


             reply	other threads:[~2026-10-14  3:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  3:24 Pengpeng Hou [this message]
2026-10-14  3:24 ` [PATCH v2 1/9] ASoC: nau8821: restore safe state after resume errors Pengpeng Hou
2026-10-14  3:24 ` [PATCH v2 2/9] ASoC: nau8824: " Pengpeng Hou
2026-10-14  3:24 ` [PATCH v2 3/9] ASoC: nau8825: " Pengpeng Hou
2026-10-14 18:18   ` Ajay Kumar Nandam
2026-10-14  3:24 ` [PATCH v2 4/9] ASoC: rt5663: " Pengpeng Hou
2026-10-14  3:24 ` [PATCH v2 5/9] ASoC: rt5682s: " Pengpeng Hou
2026-10-14  3:24 ` [PATCH v2 6/9] ASoC: rt5682: " Pengpeng Hou
2026-10-14  3:24 ` [PATCH v2 7/9] ASoC: wm8978: " Pengpeng Hou
2026-10-14  9:20   ` Charles Keepax
2026-10-14  3:24 ` [PATCH v2 8/9] ASoC: rt5640: " Pengpeng Hou
2026-10-14  3:24 ` [PATCH v2 9/9] ASoC: rt5677: " Pengpeng Hou
2026-10-14 18:43   ` Ajay Kumar Nandam

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=20261014032452.13456-1-hppiscas@163.com \
    --to=hppiscas@163.com \
    --cc=bardliao@realtek.com \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.cirrus.com \
    --cc=derek.fang@realtek.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=jack.yu@realtek.com \
    --cc=john.lin@realtek.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=oder_chiou@realtek.com \
    --cc=patches@opensource.cirrus.com \
    --cc=perex@perex.cz \
    --cc=supercraig0719@gmail.com \
    --cc=swarren@nvidia.com \
    --cc=tiwai@suse.com \
    --cc=wtli@nuvoton.com \
    --cc=yang.a.fang@intel.com \
    --cc=yong.zhi@intel.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

all inboxes | Powered by JetHome®