From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
Stephen Warren <swarren@nvidia.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: wm8903: add regulator handling
Date: Wed, 22 Mar 2017 09:06:20 +0000 [thread overview]
Message-ID: <20170322090620.GC6986@localhost.localdomain> (raw)
In-Reply-To: <CACRpkdbcudActZhifqUrb-4PFY0tTpNwt0TvpS4nUu6ptWPOJw@mail.gmail.com>
On Wed, Mar 22, 2017 at 08:24:32AM +0100, Linus Walleij wrote:
> On Mon, Mar 20, 2017 at 12:51 PM, Charles Keepax
> <ckeepax@opensource.wolfsonmicro.com> wrote:
> > On Mon, Mar 20, 2017 at 10:13:52AM +0100, Linus Walleij wrote:
>
> >> Mark: I was thinking about adding runtime PM for disabling
> >> these regulators when unused, but I'm uncertain about the
> >> interaction with DAPM in that regard. This atleast gives us
> >> control over the supplies.
> >
> > DAPM will hold a pm_runtime reference whilst the chip is active
> > so usually there isn't really much interaction to worry about.
>
> OK, so since the codec is registered on i2c's client->dev I take
> it I could use the runtime PM / suspend/resume callbacks on
> that device, and it should just work.
>
Yeah should do, wm8962 should provide a reasonably similar model
if you are looking for a handy example and feel free to drop me a
line if I can be of any help.
Thanks,
Charles
next prev parent reply other threads:[~2017-03-22 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 9:13 [PATCH] ASoC: wm8903: add regulator handling Linus Walleij
2017-03-20 11:51 ` Charles Keepax
2017-03-22 7:24 ` Linus Walleij
2017-03-22 9:06 ` Charles Keepax [this message]
[not found] ` <20170320091352.4115-1-linus.walleij-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-03-24 15:30 ` Rob Herring
2017-03-30 19:42 ` Stephen Warren
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=20170322090620.GC6986@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=swarren@nvidia.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;
as well as URLs for NNTP newsgroup(s).