From: Shawn Guo <shawn.guo@freescale.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Fabio Estevam <fabio.estevam@freescale.com>,
alsa-devel@alsa-project.org, broonie@kernel.org, lars@metafoo.de
Subject: Re: [PATCH v4] ASoC: sgtl5000: Fix the cache handling
Date: Sun, 25 May 2014 16:13:21 +0800 [thread overview]
Message-ID: <20140525081320.GB13258@dragon> (raw)
In-Reply-To: <1400958960-18775-1-git-send-email-festevam@gmail.com>
Fabio,
On Sat, May 24, 2014 at 04:16:00PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
>
> Since commit e5d80e82e32e (ASoC: sgtl5000: Convert to use regmap directly) a
> kernel oops is observed after a suspend/resume sequence.
>
> According to Mark Brown:
>
> "Looking at the code what I'd expect to happen here is that
> set_bias_level() manages the cache enable, turning on cache only mode
> just before it turns the regulators off and restoring normal mode just
> after enabling them, then calling _restore_regs() after that. The
> resume call should just be a call to set_bias_level() then.."
>
> Do as suggested and also complete the cache array with the missing registers
> so that sgtl5000_restore_regs() can properly cache the all the registers it
> needs.
>
> Reported-by: Shawn Guo <shawn.guo@freescale.com>
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
I'm not sure if it's the problem of this patch, but when I test
suspend/resume cycle with a wave playback running background, the
playback goes abnormal after system resumes back. I did this test with
your patch 'ASoC: fsl_ssi: Add suspend/resume support' applied.
The same test goes fine with wm8962 on imx6q-sabresd board.
Shawn
next prev parent reply other threads:[~2014-05-25 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 19:16 [PATCH v4] ASoC: sgtl5000: Fix the cache handling Fabio Estevam
2014-05-25 8:13 ` Shawn Guo [this message]
2014-05-26 7:26 ` Lars-Peter Clausen
2014-05-26 10:11 ` Mark Brown
2014-05-26 13:28 ` Fabio Estevam
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=20140525081320.GB13258@dragon \
--to=shawn.guo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=lars@metafoo.de \
/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.