From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
broonie@kernel.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: [RFC PATCH 0/3] ASoC: add dailink .exit() callback
Date: Thu, 5 Mar 2020 07:06:13 -0600 [thread overview]
Message-ID: <20200305130616.28658-1-pierre-louis.bossart@linux.intel.com> (raw)
While looking at reboot issues and module load/unload tests, I found
out some resources allocated in the dailink .init() callback are not
properly released - there is no existing mechanism in the soc-core to
do so.
I experimented with different solutions and the simplest seems to add
an .exit() callback. However things are not fully balanced and I could
use feedback on the approach.
This patchset includes two examples where this solution is useful, but
we have additional ones identified by Ranjani.
Pierre-Louis Bossart (3):
ASoC: soc-core: introduce exit() callback for dailinks
ASoC: Intel: bdw-rt5677: fix module load/unload issues
ASoC: Intel: kbl-rt5660: use .exit() dailink callback to release gpiod
include/sound/soc.h | 3 +++
sound/soc/intel/boards/bdw-rt5677.c | 14 ++++++++++++--
sound/soc/intel/boards/kbl_rt5660.c | 13 +++++++++++--
sound/soc/soc-core.c | 8 +++++++-
4 files changed, 33 insertions(+), 5 deletions(-)
--
2.20.1
next reply other threads:[~2020-03-05 13:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 13:06 Pierre-Louis Bossart [this message]
2020-03-05 13:06 ` [RFC PATCH 1/3] ASoC: soc-core: introduce exit() callback for dailinks Pierre-Louis Bossart
2020-03-05 18:15 ` Mark Brown
2020-03-05 13:06 ` [RFC PATCH 2/3] ASoC: Intel: bdw-rt5677: fix module load/unload issues Pierre-Louis Bossart
2020-03-05 13:25 ` Andy Shevchenko
2020-03-05 13:37 ` Pierre-Louis Bossart
2020-03-05 13:36 ` Mark Brown
2020-03-05 13:47 ` Pierre-Louis Bossart
2020-03-05 13:59 ` Mark Brown
2020-03-05 14:51 ` Pierre-Louis Bossart
2020-03-05 17:43 ` Mark Brown
2020-03-05 18:08 ` Pierre-Louis Bossart
2020-03-05 18:33 ` Mark Brown
2020-03-05 19:10 ` Mark Brown
2020-03-05 21:00 ` Curtis Malainey
2020-03-05 21:48 ` Pierre-Louis Bossart
2020-03-06 13:12 ` Mark Brown
2020-03-05 14:06 ` Amadeusz Sławiński
2020-03-05 14:11 ` Mark Brown
2020-03-05 14:27 ` Andy Shevchenko
2020-03-05 17:58 ` Mark Brown
2020-03-05 13:06 ` [RFC PATCH 3/3] ASoC: Intel: kbl-rt5660: use .exit() dailink callback to release gpiod Pierre-Louis Bossart
2020-03-05 13:27 ` Andy Shevchenko
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=20200305130616.28658-1-pierre-louis.bossart@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).