From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
alsa-devel@alsa-project.org, Liam Girdwood <lrg@ti.com>,
Stephen Warren <swarren@wwwdotorg.org>
Subject: Re: [PATCH] ASoC: core: Configure pin muxing via pinctrl when registering a DAI
Date: Tue, 25 Sep 2012 13:24:56 +0100 [thread overview]
Message-ID: <20120925122456.GF4428@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CACRpkdb3yA9Ued8nv59K+ct4BKmn2k53QXB16qTzQ21t2nvrhA@mail.gmail.com>
On Tue, Sep 25, 2012 at 01:56:13PM +0200, Linus Walleij wrote:
> In ux500 drivers we use *specific* (as opposed to generic) runtime PM
> code to e.g. get some hysteresis before a drivers clock and pins
> (etc) are put to sleep. Pure driver business.
Right, the runtime PM infrastructure is really useful for this stuff.
> > Devices that can be wake sources are an example here, if they
> > are doing that then turning them completely off may break functionality
> > but you can still turn some of the device (possibly a varying selection
> > depending on usage) off. For simple cases it works well and it'd be
> > good to have it but you end up back into ignoring errors...
> Our ux500 "sleep" state on the pins will put them into the apropriate
> wakeup mode where applicable. Since this may vary across boards
> it's even machine-specific.
> Configuring wakeup sources when going to a state named "sleep"
> seems intuitive to me atleast.
For some devices the set of wakeup sources vary depending on the current
system state - for example, if a cable is plugged into a connector we
may have to keep some additional things on to monitor activity on the
cable. This isn't the common case, for most things a sleep state works
fine, but it does come up.
next prev parent reply other threads:[~2012-09-25 12:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 7:54 [PATCH] ASoC: core: Configure pin muxing via pinctrl when registering a DAI Peter Ujfalusi
2012-09-21 11:13 ` Mark Brown
2012-09-21 13:16 ` Peter Ujfalusi
2012-09-21 14:55 ` Peter Ujfalusi
2012-09-22 15:23 ` Mark Brown
2012-09-21 16:23 ` Stephen Warren
2012-09-22 15:28 ` Mark Brown
2012-09-23 3:23 ` Stephen Warren
2012-09-24 9:20 ` Linus Walleij
2012-09-24 10:17 ` Mark Brown
2012-09-24 14:37 ` Linus Walleij
2012-09-25 11:11 ` Mark Brown
2012-09-25 11:24 ` Peter Ujfalusi
2012-09-25 11:43 ` Linus Walleij
2012-09-25 11:43 ` Mark Brown
2012-09-25 11:56 ` Linus Walleij
2012-09-25 12:24 ` Mark Brown [this message]
2012-09-25 17:00 ` Stephen Warren
2012-09-24 15:41 ` Stephen Warren
2012-09-25 11:22 ` Mark Brown
2012-09-24 8:34 ` Linus Walleij
2012-09-24 10:23 ` Mark Brown
2012-09-24 15:38 ` Stephen Warren
2012-09-22 15:18 ` 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=20120925122456.GF4428@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linus.walleij@linaro.org \
--cc=lrg@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=swarren@wwwdotorg.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 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.