From: Mark Brown <broonie@kernel.org>
To: Vinod Koul <vinod.koul@intel.com>
Cc: liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org
Subject: Applied "ASoC: Intel: Skylake: Disable async suspend" to the asoc tree
Date: Wed, 22 Jun 2016 16:28:32 +0100 [thread overview]
Message-ID: <E1bFk4u-0002HC-UN@debutante> (raw)
In-Reply-To: <1466604861-24288-3-git-send-email-vinod.koul@intel.com>
The patch
ASoC: Intel: Skylake: Disable async suspend
has been applied to the asoc tree at
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
>From 2e9dc2b645f72dcd528edbad7e35fa34d7204020 Mon Sep 17 00:00:00 2001
From: Vinod Koul <vinod.koul@intel.com>
Date: Wed, 22 Jun 2016 19:44:19 +0530
Subject: [PATCH] ASoC: Intel: Skylake: Disable async suspend
We do not support async suspend due to dependency with rest of
card and require suspend/resume be executed synchronously, mark
the device accordingly.
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Signed-off-by: Mark Brown <broonie@kernel.org>
---
sound/soc/intel/skylake/skl.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/sound/soc/intel/skylake/skl.c b/sound/soc/intel/skylake/skl.c
index 734072c79205..720efb9fd995 100644
--- a/sound/soc/intel/skylake/skl.c
+++ b/sound/soc/intel/skylake/skl.c
@@ -668,6 +668,8 @@ static int skl_probe(struct pci_dev *pci,
skl->pci_id = pci->device;
+ device_disable_async_suspend(bus->dev);
+
skl->nhlt = skl_nhlt_init(bus->dev);
if (skl->nhlt == NULL)
--
2.8.1
next prev parent reply other threads:[~2016-06-22 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 14:14 [PATCH v2 0/4] ASoC: Intel: Skylake: Disable async suspend Vinod Koul
2016-06-22 14:14 ` [PATCH v2 1/4] ASoC: Intel: Revert "ASoC: Intel: Add support for PM ops in bxt-rt298" Vinod Koul
2016-06-22 15:28 ` Applied "ASoC: Intel: Revert "ASoC: Intel: Add support for PM ops in bxt-rt298"" to the asoc tree Mark Brown
2016-06-22 14:14 ` [PATCH v2 2/4] ASoC: Intel: Skylake: Disable async suspend Vinod Koul
2016-06-22 15:28 ` Mark Brown [this message]
2016-06-22 14:14 ` [PATCH v2 3/4] ASoC: Intel: Skylake: Add pm ops for broxton-rt298 machine Vinod Koul
2016-06-22 15:28 ` Applied "ASoC: Intel: Skylake: Add pm ops for broxton-rt298 machine" to the asoc tree Mark Brown
2016-06-22 14:14 ` [PATCH v2 4/4] ASoC: Intel: Skylake: Update comment style Vinod Koul
2016-06-22 15:28 ` Applied "ASoC: Intel: Skylake: Update comment style" to the asoc tree 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=E1bFk4u-0002HC-UN@debutante \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--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.