From: Mark Brown <broonie@kernel.org>
To: jiada_wang@mentor.com
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
kuninori.morimoto.gx@renesas.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] ASoC: pcm3168a: Don't disable pcm3168a when CONFIG_PM defined
Date: Wed, 28 Nov 2018 16:22:11 +0000 [thread overview]
Message-ID: <20181128162211.GL6828@sirena.org.uk> (raw)
In-Reply-To: <20181128122612.17820-1-jiada_wang@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
On Wed, Nov 28, 2018 at 09:26:12PM +0900, jiada_wang@mentor.com wrote:
> From: Jiada Wang <jiada_wang@mentor.com>
>
> pcm3168 codec support runtime_[resume|suspend], whenever it
> is not active, it enters suspend mode, and it's clock and regulators
> will be disabled. so there is no need to disable them again in
> remove callback. Otherwise we got following kernel warnings,
> when unload pcm3168a driver
>
> [ 222.257514] unbalanced disables for amp-en-regulator
> [ 222.262526] ------------[ cut here ]------------
> [ 222.267158] WARNING: CPU: 0 PID: 2423 at drivers/regulator/core.c:2264 _regulator_disable+0x28/0x108
> [ 222.276291] Modules linked in:
> [ 222.279343] snd_soc_pcm3168a_i2c(-)
Please think hard before including complete backtraces in upstream
reports, they are very large and contain almost no useful information
relative to their size so often obscure the relevant content in your
message. If part of the backtrace is usefully illustrative then it's
usually better to pull out the relevant sections.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-11-28 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 12:26 jiada_wang
2018-11-28 16:22 ` Mark Brown [this message]
2018-11-28 17:19 ` Applied "ASoC: pcm3168a: Don't disable pcm3168a when CONFIG_PM defined" to the asoc tree 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=20181128162211.GL6828@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=jiada_wang@mentor.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--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
all inboxes | Powered by JetHome®