All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, Jaska Uimonen <jaska.uimonen@intel.com>,
	broonie@kernel.org,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: [alsa-devel] [PATCH 4/4] ASoC: intel: sof_rt5682: add remove function to disable jack
Date: Fri, 27 Sep 2019 15:14:08 -0500	[thread overview]
Message-ID: <20190927201408.925-5-pierre-louis.bossart@linux.intel.com> (raw)
In-Reply-To: <20190927201408.925-1-pierre-louis.bossart@linux.intel.com>

From: Jaska Uimonen <jaska.uimonen@intel.com>

When removing sof module the rt5682 jack handler will oops
if jack detection is not disabled. So add remove function,
which disables the jack detection.

Signed-off-by: Jaska Uimonen <jaska.uimonen@intel.com>
Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
---
 sound/soc/intel/boards/sof_rt5682.c | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/sound/soc/intel/boards/sof_rt5682.c b/sound/soc/intel/boards/sof_rt5682.c
index 57b4ef75be15..5ce643d62faf 100644
--- a/sound/soc/intel/boards/sof_rt5682.c
+++ b/sound/soc/intel/boards/sof_rt5682.c
@@ -648,8 +648,24 @@ static int sof_audio_probe(struct platform_device *pdev)
 					  &sof_audio_card_rt5682);
 }
 
+static int sof_rt5682_remove(struct platform_device *pdev)
+{
+	struct snd_soc_card *card = platform_get_drvdata(pdev);
+	struct snd_soc_component *component = NULL;
+
+	for_each_card_components(card, component) {
+		if (!strcmp(component->name, rt5682_component[0].name)) {
+			snd_soc_component_set_jack(component, NULL, NULL);
+			break;
+		}
+	}
+
+	return 0;
+}
+
 static struct platform_driver sof_audio = {
 	.probe = sof_audio_probe,
+	.remove = sof_rt5682_remove,
 	.driver = {
 		.name = "sof_rt5682",
 		.pm = &snd_soc_pm_ops,
-- 
2.20.1

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2019-09-27 20:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27 20:14 [alsa-devel] [PATCH 0/4] ASoC: Intel: boards: improvements for RT5651/82-based platforms Pierre-Louis Bossart
2019-09-27 20:14 ` [alsa-devel] [PATCH 1/4] ASoC: intel: bytcr_rt5651: add null check to support_button_press Pierre-Louis Bossart
2019-10-01 17:56   ` [alsa-devel] Applied "ASoC: intel: bytcr_rt5651: add null check to support_button_press" to the asoc tree Mark Brown
2019-09-27 20:14 ` [alsa-devel] [PATCH 2/4] ASoC: intel: sof_rt5682: use separate route map for dmic Pierre-Louis Bossart
2019-10-01 17:56   ` [alsa-devel] Applied "ASoC: intel: sof_rt5682: use separate route map for dmic" to the asoc tree Mark Brown
2019-09-27 20:14 ` [alsa-devel] [PATCH 3/4] ASoC: rt5682: add NULL handler to set_jack function Pierre-Louis Bossart
2019-10-01 17:56   ` [alsa-devel] Applied "ASoC: rt5682: add NULL handler to set_jack function" to the asoc tree Mark Brown
2019-09-27 20:14 ` Pierre-Louis Bossart [this message]
2019-10-01 17:56   ` [alsa-devel] Applied "ASoC: intel: sof_rt5682: add remove function to disable jack" " 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=20190927201408.925-5-pierre-louis.bossart@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jaska.uimonen@intel.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 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.