From: Stefan Binding <sbinding@opensource.cirrus.com>
To: Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Cc: <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>,
Stefan Binding <sbinding@opensource.cirrus.com>
Subject: [PATCH v1 4/4] ALSA: hda/realtek: Delete cs35l41 component master during free
Date: Fri, 14 Apr 2023 16:25:52 +0100 [thread overview]
Message-ID: <20230414152552.574502-5-sbinding@opensource.cirrus.com> (raw)
In-Reply-To: <20230414152552.574502-1-sbinding@opensource.cirrus.com>
This ensures that the driver is properly cleaned up when freed.
Signed-off-by: Stefan Binding <sbinding@opensource.cirrus.com>
---
sound/pci/hda/patch_realtek.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 3b9f077a227f7..bbeffbb84091e 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -6757,6 +6757,8 @@ static void cs35l41_generic_fixup(struct hda_codec *cdc, int action, const char
else
spec->gen.pcm_playback_hook = comp_generic_playback_hook;
break;
+ case HDA_FIXUP_ACT_FREE:
+ component_master_del(dev, &comp_master_ops);
}
}
--
2.34.1
next prev parent reply other threads:[~2023-04-14 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 15:25 [PATCH v1 0/4] Fixes and cleanup for CS35L41 HDA Stefan Binding
2023-04-14 15:25 ` [PATCH v1 1/4] ALSA: hda: cs35l41: Clean up Firmware Load Controls Stefan Binding
2023-04-14 15:25 ` [PATCH v1 2/4] ALSA: hda: cs35l41: Fix endian conversions Stefan Binding
2023-04-14 15:25 ` [PATCH v1 3/4] ALSA: cs35l41: Fix default regmap values for some registers Stefan Binding
2023-04-14 15:29 ` Mark Brown
2023-04-14 15:25 ` Stefan Binding [this message]
2023-05-23 20:39 ` (subset) [PATCH v1 0/4] Fixes and cleanup for CS35L41 HDA 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=20230414152552.574502-5-sbinding@opensource.cirrus.com \
--to=sbinding@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox