From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: alsa-devel@alsa-project.org
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Mark Brown <broonie@kernel.org>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: [PATCH 0/7] ASoC: Intel: Baytrail SST suspend/resume support
Date: Thu, 8 May 2014 16:07:20 +0300 [thread overview]
Message-ID: <1399554447-16297-1-git-send-email-jarkko.nikula@linux.intel.com> (raw)
This set adds suspend/resume support to Baytrail SST. This is
implemented by putting the DSP into reset and by releasing driver
resources before suspend. In resume path the DSP is rebooted in normal
boot state. Active streams are restored by restarting them from last
known buffer position before suspend.
Patches 1-5 are preparing for the suspend/resume and patch 6 implements
the core logic that takes care of stopping the DSP before suspend and
restarting it again after resume. Patch 7 removes ignore_suspend flag
from byt-rt5640 machine driver since it doesn't have use at the moment
and adds suspend/resume callbacks that are hooked to ASoC core. This
takes care that active stream will be paused and resumed over
suspend/resume cycle on byt-rt5640 machine.
Jarkko Nikula (5):
ASoC: Intel: Sample Baytrail DSP DMA pointer only after each period
ASoC: Intel: Simplify Baytrail stream control IPC construction
ASoC: Intel: Pass stream start position to sst_byt_stream_start()
ASoC: Intel: Move Baytrail extended fw address saving to
sst_byt_boot()
ASoC: Intel: Allow byt-5640 machine driver and SST core go to suspend
Liam Girdwood (2):
ASoC: Intel: Allow Rx/Tx message list can be cleared prior to suspend
ASoC: Intel: Add Baytrail suspend/resume support
sound/soc/intel/byt-rt5640.c | 14 +++-
sound/soc/intel/sst-baytrail-dsp.c | 14 ++--
sound/soc/intel/sst-baytrail-ipc.c | 124 ++++++++++++++++++++++++++++------
sound/soc/intel/sst-baytrail-ipc.h | 7 +-
sound/soc/intel/sst-baytrail-pcm.c | 135 ++++++++++++++++++++++++++++++++-----
5 files changed, 249 insertions(+), 45 deletions(-)
--
2.0.0.rc0
next reply other threads:[~2014-05-08 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 13:07 Jarkko Nikula [this message]
2014-05-08 13:07 ` [PATCH 1/7] ASoC: Intel: Sample Baytrail DSP DMA pointer only after each period Jarkko Nikula
2014-05-08 13:07 ` [PATCH 2/7] ASoC: Intel: Simplify Baytrail stream control IPC construction Jarkko Nikula
2014-05-08 13:07 ` [PATCH 3/7] ASoC: Intel: Pass stream start position to sst_byt_stream_start() Jarkko Nikula
2014-05-08 13:07 ` [PATCH 4/7] ASoC: Intel: Move Baytrail extended fw address saving to sst_byt_boot() Jarkko Nikula
2014-05-08 13:07 ` [PATCH 5/7] ASoC: Intel: Allow Rx/Tx message list can be cleared prior to suspend Jarkko Nikula
2014-05-08 13:07 ` [PATCH 6/7] ASoC: Intel: Add Baytrail suspend/resume support Jarkko Nikula
2014-05-08 13:07 ` [PATCH 7/7] ASoC: Intel: Allow byt-5640 machine driver and SST core go to suspend Jarkko Nikula
2014-05-12 21:02 ` [PATCH 0/7] ASoC: Intel: Baytrail SST suspend/resume support 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=1399554447-16297-1-git-send-email-jarkko.nikula@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox