From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/9] ASoC: Intel: sst: Fix Bay Trail suspend/resume issues
Date: Mon, 19 Feb 2018 15:53:30 +0200 [thread overview]
Message-ID: <CAHp75Ved8FH+ZvzEbPjHj2uwTg4pXvky3fjxHFsk-352V17obg@mail.gmail.com> (raw)
In-Reply-To: <20180218220146.22485-1-hdegoede@redhat.com>
On Mon, Feb 19, 2018 at 12:01 AM, Hans de Goede <hdegoede@redhat.com> wrote:
> Hi All,
>
> Here is a series fixing suspend/resume errors (and broken audio after
> resume) on Bay Trail devices.
>
> Cherry Trail devices also do not like being suspend while audio is
> playing, but with different sypmtoms instead of SST_ERR_INVALID_STREAM_ID
> errors, if a stream was playing (being allocated is fine, playing is a
> problem) before suspend then after resume we get the following errors:
>
> [ 2312.389974] intel_sst_acpi 808622A8:00: sst: Busy wait failed, cant send this msg
> [ 2312.597976] intel_sst_acpi 808622A8:00: sst: Busy wait failed, cant send this msg
> ...
>
> Until the stream is stopped and restarted after which things work fine
> again. I've tried enabling the quirk this commit adds for Cherry Trail
> devices too, but that does not help. If anyone has any clues about the CHT
> problem, please let me know.
Good fix!
FWIW,
Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2018-02-19 13:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 22:01 [PATCH 0/9] ASoC: Intel: sst: Fix Bay Trail suspend/resume issues Hans de Goede
2018-02-18 22:01 ` [PATCH 1/9] ASoC: Intel: sst: Fix error-code check in sst_pause_stream() Hans de Goede
2018-02-19 13:47 ` Andy Shevchenko
2018-02-19 14:00 ` Hans de Goede
2018-02-18 22:01 ` [PATCH 2/9] ASoC: Intel: sst: Remove 2 unused members from stream_info struct Hans de Goede
2018-02-18 22:01 ` [PATCH 3/9] ASoC: Intel: sst: Remove unnecessary sst_init_stream() function Hans de Goede
2018-02-18 22:01 ` [PATCH 4/9] ASoC: Intel: sst: Remove unused STREAM_DECODE and STREAM_RESET states Hans de Goede
2018-02-18 22:01 ` [PATCH 5/9] ASoC: Intel: sst: Add sst_realloc_stream() function Hans de Goede
2018-02-18 22:01 ` [PATCH 6/9] ASoC: Intel: sst: Free streams on suspend, re-alloc on resume Hans de Goede
2018-02-19 13:51 ` Andy Shevchenko
2018-02-19 14:02 ` Hans de Goede
2018-02-19 16:29 ` Mark Brown
2018-02-19 16:32 ` Hans de Goede
2018-02-19 16:35 ` Mark Brown
2018-02-18 22:01 ` [PATCH 7/9] ASoc: rt5651: Fix regcache sync errors " Hans de Goede
2018-02-18 22:01 ` [PATCH 8/9] ASoC: Intel: bytcr_rt5640: Drop unwanted ignore_suspend settings Hans de Goede
2018-03-01 16:22 ` Mark Brown
2018-03-01 16:26 ` Hans de Goede
2018-03-01 16:48 ` Mark Brown
2018-03-01 16:58 ` Hans de Goede
2018-03-01 17:17 ` Mark Brown
2018-03-04 14:11 ` Hans de Goede
2018-03-05 13:50 ` Hans de Goede
2018-03-05 15:34 ` Mark Brown
2018-02-18 22:01 ` [PATCH 9/9] ASoC: Intel: bytcr_rt5651: " Hans de Goede
2018-02-19 13:53 ` Andy Shevchenko [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=CAHp75Ved8FH+ZvzEbPjHj2uwTg4pXvky3fjxHFsk-352V17obg@mail.gmail.com \
--to=andy.shevchenko@gmail.com \
--cc=broonie@kernel.org \
--cc=hdegoede@redhat.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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).