All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Binding <sbinding@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	patches@opensource.cirrus.com,
	Stefan Binding <sbinding@opensource.cirrus.com>
Subject: [PATCH v1 0/7] Fixes and improvements in CS35L41 HDA driver for System Suspend/Resume
Date: Fri, 20 Nov 2026 16:10:46 +0000	[thread overview]
Message-ID: <20261120161136.157593-1-sbinding@opensource.cirrus.com> (raw)

A number of issues in system suspend and system resume have been reported
on the CS35L41 HDA driver. These patches fix some of the issues, as well
as improve the suspend/resume code in the driver.

The main issues resolved are:
- CS35L41 boot issues after system resume (on SPI systems using S4 hibernation)
- a deadlock during system suspend due to a race condition with the filesystem

Also included is a patch to prevent issues with IRQs during suspend/resume.

In addition, there are 3 patches which prepare the driver for these
improvements and fixes:
- ALSA: hda: cs35l41: Remove redundant lock_system_sleep() calls
- ALSA: hda: cs35l41: Unset irq if not used or configured
- ALSA: hda/cs35l41: Remove support for alternative firmware types

Stefan Binding (7):
  ALSA: hda: cs35l41: Remove redundant lock_system_sleep() calls
  ASoC: cs35l41: Prevent software reset when using SPI
  ALSA: hda: cs35l41: Unset irq if not used or configured
  ALSA: hda/cs35l41: Split System Suspend/Resume callbacks
  ALSA: hda/cs35l41: Remove support for alternative firmware types
  ALSA: hda/cs35l41: Store filenames of successfully loaded firmware and
    tunings
  ALSA: hda/cs35l41: rework how firmware requests are queued and flushed
    to prevent races

 sound/hda/codecs/side-codecs/cs35l41_hda.c | 362 +++++++++++++--------
 sound/hda/codecs/side-codecs/cs35l41_hda.h |   7 +-
 sound/soc/codecs/cs35l41-lib.c             |  51 ++-
 3 files changed, 275 insertions(+), 145 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-11-20 16:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 16:10 Stefan Binding [this message]
2026-11-20 16:10 ` [PATCH v1 1/7] ALSA: hda: cs35l41: Remove redundant lock_system_sleep() calls Stefan Binding
2026-11-20 16:10 ` [PATCH v1 2/7] ASoC: cs35l41: Prevent software reset when using SPI Stefan Binding
2026-11-20 16:22   ` sashiko-bot
2026-11-20 16:10 ` [PATCH v1 3/7] ALSA: hda: cs35l41: Unset irq if not used or configured Stefan Binding
2026-11-20 16:10 ` [PATCH v1 4/7] ALSA: hda/cs35l41: Split System Suspend/Resume callbacks Stefan Binding
2026-11-20 16:27   ` sashiko-bot
2026-11-20 16:10 ` [PATCH v1 5/7] ALSA: hda/cs35l41: Remove support for alternative firmware types Stefan Binding
2026-11-20 16:10 ` [PATCH v1 6/7] ALSA: hda/cs35l41: Store filenames of successfully loaded firmware and tunings Stefan Binding
2026-11-20 16:10 ` [PATCH v1 7/7] ALSA: hda/cs35l41: rework how firmware requests are queued and flushed to prevent races Stefan Binding
2026-11-20 16:41   ` 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=20261120161136.157593-1-sbinding@opensource.cirrus.com \
    --to=sbinding@opensource.cirrus.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=perex@perex.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.