From: Takashi Iwai <tiwai@suse.de>
To: linux-sound@vger.kernel.org
Cc: David Rhodes <david.rhodes@cirrus.com>,
Richard Fitzgerald <rf@opensource.cirrus.com>,
patches@opensource.cirrus.com,
Shenghao Ding <shenghao-ding@ti.com>, Kevin Lu <kevin-lu@ti.com>,
Baojun Xu <baojun.xu@ti.com>
Subject: [PATCH 00/25] ALSA: hda: Use auto-cleanup macros
Date: Mon, 11 Aug 2025 12:07:34 +0200 [thread overview]
Message-ID: <20250811100807.7962-1-tiwai@suse.de> (raw)
This is a slightly largish patch set for cleaning up HD-audio code to
use the auto-cleanup macros like guard(), CLASS() and __free() for
managing the locking and temporary buffers.
All patches are only about code refactoring and no behavior changes
intended.
Takashi
===
Takashi Iwai (25):
ALSA: hda: Introduce auto cleanup macros for PM
ALSA: hda/ca0132: Use cleanup macros for PM controls
ALSA: hda/hdmi: Use cleanup macros for PM controls
ALSA: hda/realtek: Use cleanup macros for PM controls
ALSA: hda/common: Use cleanup macros for PM controls
ALSA: hda: Use auto cleanup macros for DSP loader locks
ALSA: hda/common: Use guard() for mutex locks
ALSA: hda/core: Use guard() for mutex locks
ALSA: hda/ca0132: Use guard() for mutex locks
ALSA: hda/hdmi: Use guard() for mutex locks
ALSA: hda/realtek: Use guard() for mutex locks
ALSA: hda/cs35l41: Use guard() for mutex locks
ALSA: hda/tas2781: Use guard() for mutex locks
ALSA: hda/cs8409: Use guard() for mutex locks
ALSA: hda/component: Use guard() for mutex locks
ALSA: hda/generic: Use guard() for mutex locks
ALSA: hda/analog: Use guard() for mutex locks
ALSA: hda/intel: Use guard() for mutex locks
ALSA: hda/common: Use auto cleanup for temporary buffers
ALSA: hda/realtek: Use auto cleanup for temporary buffers
ALSA: hda/generic: Use auto cleanup for temporary buffers
ALSA: hda/ext: Use guard() for spinlocks
ALSA: hda/core: Use guard() for spinlocks
ALSA: hda/common: Use guard() for spinlocks
ALSA: hda/intel: Use guard() for spinlocks
include/sound/hda_codec.h | 30 ++
include/sound/hdaudio.h | 1 +
sound/hda/codecs/analog.c | 3 +-
sound/hda/codecs/ca0132.c | 276 +++++++-----------
sound/hda/codecs/cirrus/cs8409.c | 22 +-
sound/hda/codecs/generic.c | 76 ++---
sound/hda/codecs/hdmi/hdmi.c | 199 +++++--------
sound/hda/codecs/hdmi/nvhdmi-mcp.c | 3 +-
sound/hda/codecs/realtek/alc268.c | 3 +-
sound/hda/codecs/realtek/alc269.c | 3 +-
sound/hda/codecs/realtek/realtek.c | 22 +-
sound/hda/codecs/side-codecs/cs35l41_hda.c | 110 +++----
sound/hda/codecs/side-codecs/hda_component.c | 15 +-
sound/hda/codecs/side-codecs/hda_component.h | 3 +-
.../hda/codecs/side-codecs/tas2781_hda_i2c.c | 53 ++--
sound/hda/common/codec.c | 129 ++++----
sound/hda/common/controller.c | 124 ++++----
sound/hda/common/proc.c | 4 +-
sound/hda/common/sysfs.c | 110 +++----
sound/hda/controllers/intel.c | 14 +-
sound/hda/core/bus.c | 8 +-
sound/hda/core/component.c | 6 +-
sound/hda/core/controller.c | 58 ++--
sound/hda/core/device.c | 23 +-
sound/hda/core/ext/controller.c | 6 +-
sound/hda/core/ext/stream.c | 38 ++-
sound/hda/core/regmap.c | 35 +--
sound/hda/core/stream.c | 31 +-
28 files changed, 559 insertions(+), 846 deletions(-)
--
2.50.1
next reply other threads:[~2025-08-11 10:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 10:07 Takashi Iwai [this message]
2025-08-11 10:07 ` [PATCH 01/25] ALSA: hda: Introduce auto cleanup macros for PM Takashi Iwai
2025-08-11 10:07 ` [PATCH 02/25] ALSA: hda/ca0132: Use cleanup macros for PM controls Takashi Iwai
2025-08-11 10:07 ` [PATCH 03/25] ALSA: hda/hdmi: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 04/25] ALSA: hda/realtek: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 05/25] ALSA: hda/common: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 06/25] ALSA: hda: Use auto cleanup macros for DSP loader locks Takashi Iwai
2025-08-11 10:07 ` [PATCH 07/25] ALSA: hda/common: Use guard() for mutex locks Takashi Iwai
2025-08-11 10:07 ` [PATCH 08/25] ALSA: hda/core: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 09/25] ALSA: hda/ca0132: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 10/25] ALSA: hda/hdmi: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 11/25] ALSA: hda/realtek: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 12/25] ALSA: hda/cs35l41: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 13/25] ALSA: hda/tas2781: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 14/25] ALSA: hda/cs8409: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 15/25] ALSA: hda/component: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 16/25] ALSA: hda/generic: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 17/25] ALSA: hda/analog: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 18/25] ALSA: hda/intel: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 19/25] ALSA: hda/common: Use auto cleanup for temporary buffers Takashi Iwai
2025-08-11 10:07 ` [PATCH 20/25] ALSA: hda/realtek: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 21/25] ALSA: hda/generic: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 22/25] ALSA: hda/ext: Use guard() for spinlocks Takashi Iwai
2025-08-11 10:07 ` [PATCH 23/25] ALSA: hda/core: " Takashi Iwai
2025-08-13 14:07 ` Andy Shevchenko
2025-08-13 14:10 ` Andy Shevchenko
2025-08-13 14:19 ` Takashi Iwai
2025-08-11 10:07 ` [PATCH 24/25] ALSA: hda/common: " Takashi Iwai
2025-08-11 10:07 ` [PATCH 25/25] ALSA: hda/intel: " Takashi Iwai
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=20250811100807.7962-1-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=baojun.xu@ti.com \
--cc=david.rhodes@cirrus.com \
--cc=kevin-lu@ti.com \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=shenghao-ding@ti.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