public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Adam Ford <aford173@gmail.com>
Cc: patches@opensource.cirrus.com,
	ALSA Development Mailing List <alsa-devel@alsa-project.org>,
	Takashi Iwai <tiwai@suse.com>,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: WM8962 crashing on suspend
Date: Tue, 26 Apr 2022 18:32:41 +0100	[thread overview]
Message-ID: <YmgsuUmHwffwP6X9@sirena.org.uk> (raw)
In-Reply-To: <CAHCN7xJuAuGmSQsmBfg-C6jOdJmf1Li=YWp7Jdi29nU3kk1GcA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

On Tue, Apr 26, 2022 at 11:36:26AM -0500, Adam Ford wrote:
> I have an imx8m Mini with a wm8962 codec.  If I run a speaker test and
> suspend the board while the speaker test is running, I get the
> following upon wake:
> 
> wm8962 3-001a: ASoC: error at soc_component_read_no_lock on wm8962.3-001a: -16
> 
> This message repeats itself over and over again.  If I attempt to use
> any audio, it fails until I reboot the board.
> 
> If I run the audio test, then exit and suspend, the audio works upon
> resume, so it appears to be related to suspending while running.
> 
> I am hoping someone might have a suggestion as to what I might be able
> to do or try to allow this to successfully suspend and resume if the
> device is playing sound.

I do note that wm8962 doesn't have any system suspend code which is
possibly an issue if power is lost during suspend, it only has runtime
PM operations.  If the device was runtime idle before suspend those will
figure everything out, if the device was active they won't kick in.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2022-04-26 17:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 16:36 WM8962 crashing on suspend Adam Ford
2022-04-26 17:32 ` Mark Brown [this message]
2022-04-26 17:41 ` Charles Keepax
2022-04-27 13:12   ` Adam Ford
2022-04-27 13:21     ` Mark Brown
2022-04-27 14:58       ` Charles Keepax
2022-04-27 14:57     ` Charles Keepax
2022-04-27 15:24       ` Mark Brown
2022-04-27 16:48         ` Charles Keepax
2022-04-27 16:54           ` Adam Ford
2022-04-28  8:23             ` Charles Keepax
2022-04-28 12:21               ` Adam Ford
2022-04-28 12:45                 ` Mark Brown
2022-04-27 17:02           ` 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=YmgsuUmHwffwP6X9@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=aford173@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lgirdwood@gmail.com \
    --cc=patches@opensource.cirrus.com \
    --cc=tiwai@suse.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