alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: alsa-devel@alsa-project.org
Cc: tiwai@suse.de, patches.audio@intel.com,
	liam.r.girdwood@linux.intel.com,
	Vinod Koul <vinod.koul@intel.com>,
	broonie@kernel.org, Jeeja KP <jeeja.kp@intel.com>
Subject: [PATCH v2 02/13] ASoC: Intel: Skylake: Fix to set pipe state to invalid when deleting
Date: Sat, 12 Dec 2015 17:36:22 +0530	[thread overview]
Message-ID: <1449921993-21101-3-git-send-email-vinod.koul@intel.com> (raw)
In-Reply-To: <1449921993-21101-1-git-send-email-vinod.koul@intel.com>

From: Jeeja KP <jeeja.kp@intel.com>

When pipeline is deleted, set the pipeline state to invalid state.

Signed-off-by: Jeeja KP <jeeja.kp@intel.com>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
---
 sound/soc/intel/skylake/skl-messages.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/sound/soc/intel/skylake/skl-messages.c b/sound/soc/intel/skylake/skl-messages.c
index 46310d9ac008..de6dac496a0d 100644
--- a/sound/soc/intel/skylake/skl-messages.c
+++ b/sound/soc/intel/skylake/skl-messages.c
@@ -849,6 +849,8 @@ int skl_delete_pipe(struct skl_sst *ctx, struct skl_pipe *pipe)
 		ret = skl_ipc_delete_pipeline(&ctx->ipc, pipe->ppl_id);
 		if (ret < 0)
 			dev_err(ctx->dev, "Failed to delete pipeline\n");
+
+		pipe->state = SKL_PIPE_INVALID;
 	}
 
 	return ret;
-- 
1.9.1

  parent reply	other threads:[~2015-12-12 12:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-12 12:06 [PATCH v2 00/13] ASoC: Intel: Skylake: Update to SKL driver Vinod Koul
2015-12-12 12:06 ` [PATCH v2 01/13] ASoC: Intel: Skylake: Clear stream registers before stream setup Vinod Koul
2015-12-12 12:06 ` Vinod Koul [this message]
2015-12-12 12:06 ` [PATCH v2 03/13] ALSA: hdac: Add support for hda DMA Resume capability Vinod Koul
2015-12-12 12:06 ` [PATCH v2 04/13] ALSA: hdac: couple the hda DMA stream in cleanup Vinod Koul
2015-12-12 12:06 ` [PATCH v2 05/13] ALSA: hdac: Increase timeout value for link power check Vinod Koul
2015-12-12 12:06 ` [PATCH v2 06/13] ALSA: hdac: add snd_hdac_ext_bus_link_power_up_all Vinod Koul
2015-12-12 12:06 ` [PATCH v2 07/13] ASoC: Intel: Skylake: fix reset controller sequencing Vinod Koul
2015-12-12 12:06 ` [PATCH v2 08/13] ASoC: Intel: Skylake: Use CGCTL.MISCBDCGE for Phrase detection notification Vinod Koul
     [not found]   ` <201512130213.fd9SElQX%fengguang.wu@intel.com>
2015-12-14  4:22     ` Vinod Koul
2015-12-12 12:06 ` [PATCH v2 09/13] ASoC: Intel: Skylake: manage link power in active suspend Vinod Koul
2015-12-12 12:06 ` [PATCH v2 10/13] ASoC: Intel: Skylake: enable interrupt as wake source " Vinod Koul
2015-12-12 12:06 ` [PATCH v2 11/13] ASoC: Intel: Skylake: Add DMA resume position in Trigger resume/suspend Vinod Koul
2015-12-12 12:06 ` [PATCH v2 12/13] ASoC: Intel: Skylake: Reconfigure Link stream on suspend/resume Vinod Koul
2015-12-12 12:06 ` [PATCH v2 13/13] ASoC: Intel: Skylake: Add Resume capability in PCM info Vinod Koul

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=1449921993-21101-3-git-send-email-vinod.koul@intel.com \
    --to=vinod.koul@intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jeeja.kp@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=patches.audio@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 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).