All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: stable@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	Vinod Koul <vinod.koul@intel.com>
Subject: Re: [PATCH v4.4.x] ASoC: intel: Fix PM and non-atomic crash in bytcr drivers
Date: Wed, 3 May 2017 15:35:00 -0700	[thread overview]
Message-ID: <20170503223500.GA15587@kroah.com> (raw)
In-Reply-To: <20170501070927.16357-2-tiwai@suse.de>

On Mon, May 01, 2017 at 09:09:27AM +0200, Takashi Iwai wrote:
> commit 6e4cac23c5a648d50b107d1b53e9c4e1120c7943 upstream.
> 
> The FE setups of Intel SST bytcr_rt5640 and bytcr_rt5651 drivers carry
> the ignore_suspend flag, and this prevents the suspend/resume working
> properly while the stream is running, since SST core code has the
> check of the running streams and returns -EBUSY.  Drop these
> superfluous flags for fixing the behavior.
> 
> Also, the bytcr_rt5640 driver lacks of nonatomic flag in some FE
> definitions, which leads to the kernel Oops at suspend/resume like:
> 
>   BUG: scheduling while atomic: systemd-sleep/3144/0x00000003
>   Call Trace:
>    dump_stack+0x5c/0x7a
>    __schedule_bug+0x55/0x70
>    __schedule+0x63c/0x8c0
>    schedule+0x3d/0x90
>    schedule_timeout+0x16b/0x320
>    ? del_timer_sync+0x50/0x50
>    ? sst_wait_timeout+0xa9/0x170 [snd_intel_sst_core]
>    ? sst_wait_timeout+0xa9/0x170 [snd_intel_sst_core]
>    ? remove_wait_queue+0x60/0x60
>    ? sst_prepare_and_post_msg+0x275/0x960 [snd_intel_sst_core]
>    ? sst_pause_stream+0x9b/0x110 [snd_intel_sst_core]
>    ....
> 
> This patch addresses these appropriately, too.
> 
> [tiwai: applied only to bytcr_rt5640 as bytcr_rt5651 isn't present in
>  4.4.x yet]
> 
> Signed-off-by: Takashi Iwai <tiwai@suse.de>
> Acked-by: Vinod Koul <vinod.koul@intel.com>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Cc: <stable@vger.kernel.org> # v4.1+
> ---
> 
> This is the patch modified to be applicable to 4.4.x that failed in
> your previous queue.

Thanks for the backport, now applied.

greg k-h

      reply	other threads:[~2017-05-03 22:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-01  7:09 [PATCH v4.4.x] ASoC: intel: Fix PM and non-atomic crash in bytcr drivers Takashi Iwai
2017-05-01  7:09 ` Takashi Iwai
2017-05-03 22:35   ` Greg Kroah-Hartman [this message]

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=20170503223500.GA15587@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@intel.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 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.