From: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
To: lgirdwood@gmail.com, broonie@kernel.org
Cc: alsa-devel@alsa-project.org, kai.vehmanen@linux.intel.com,
pierre-louis.bossart@linux.intel.com,
ranjani.sridharan@linux.intel.com,
amadeuszx.slawinski@linux.intel.com, cujomalainey@chromium.org,
yung-chuan.liao@linux.intel.com
Subject: [PATCH v2 0/3] ASoC: SOF: Fixes for suspend after firmware crash
Date: Tue, 20 Dec 2022 14:56:26 +0200 [thread overview]
Message-ID: <20221220125629.8469-1-peter.ujfalusi@linux.intel.com> (raw)
Hi,
This is the followup series for the v1 sent out by Ranjani [1]. Unfortunately
Ranjani was dragged away to another issue and could not send the update herself.
Changes since v1:
- In patch 2, move the tear_down_all_pipelines call instead of duplicating it
Amadeusz: I have kept the check as it is:
if (tplg_ops && tplg_ops->tear_down_all_pipelines)
I'm preparing the ops optionality change series which would require this change.
[1] https://lore.kernel.org/alsa-devel/20221215185347.1457541-1-ranjani.sridharan@linux.intel.com/T/#t
Regards,
Peter
---
Curtis Malainey (1):
ASoC: SOF: Add FW state to debugfs
Ranjani Sridharan (2):
ASoC: SOF: pm: Set target state earlier
ASoC: SOF: pm: Always tear down pipelines before DSP suspend
sound/soc/sof/debug.c | 4 +++-
sound/soc/sof/pm.c | 9 ++++-----
2 files changed, 7 insertions(+), 6 deletions(-)
--
2.39.0
next reply other threads:[~2022-12-20 12:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 12:56 Peter Ujfalusi [this message]
2022-12-20 12:56 ` [PATCH v2 1/3] ASoC: SOF: pm: Set target state earlier Peter Ujfalusi
2022-12-20 12:56 ` [PATCH v2 2/3] ASoC: SOF: pm: Always tear down pipelines before DSP suspend Peter Ujfalusi
2022-12-20 12:56 ` [PATCH v2 3/3] ASoC: SOF: Add FW state to debugfs Peter Ujfalusi
2022-12-27 0:14 ` [PATCH v2 0/3] ASoC: SOF: Fixes for suspend after firmware crash Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2022-12-20 12:56 Peter Ujfalusi
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=20221220125629.8469-1-peter.ujfalusi@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cujomalainey@chromium.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=yung-chuan.liao@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