From: Mark Brown <broonie@kernel.org>
To: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, lars@metafoo.de,
lgirdwood@gmail.com, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH v3 5/5] ASoC: arizona: Use auto disable muxes for routing
Date: Wed, 6 May 2015 17:16:37 +0100 [thread overview]
Message-ID: <20150506161637.GX22845@sirena.org.uk> (raw)
In-Reply-To: <1430480247-28753-5-git-send-email-ckeepax@opensource.wolfsonmicro.com>
[-- Attachment #1.1: Type: text/plain, Size: 438 bytes --]
On Fri, May 01, 2015 at 12:37:27PM +0100, Charles Keepax wrote:
> The mixer core on the Arizona devices is powered up whenever any routing
> is non-zero. This patch saves a little power and avoids a few difficult
> corner cases (around the mixer core being powered whilst there is no
> clock available), by using the autodisable mux functionality to only
> write out the settings for the muxes when they are powered up.
Applied, thanks.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-05-06 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 11:37 [PATCH v3 1/5] ASoC: Correct typo in SOC_VALUE_ENUM_SINGLE macro Charles Keepax
2015-05-01 11:37 ` [PATCH v3 2/5] ASoC: dapm: Remove local OOM error message Charles Keepax
2015-05-04 12:04 ` Mark Brown
2015-05-01 11:37 ` [PATCH v3 3/5] ASoC: dapm: Append "Autodisable" to autodisable widget names Charles Keepax
2015-05-04 12:04 ` Mark Brown
2015-05-01 11:37 ` [PATCH v3 4/5] ASoC: dapm: Add support for autodisable mux controls Charles Keepax
2015-05-06 16:12 ` Mark Brown
2015-05-01 11:37 ` [PATCH v3 5/5] ASoC: arizona: Use auto disable muxes for routing Charles Keepax
2015-05-06 16:16 ` Mark Brown [this message]
2015-05-01 14:31 ` [PATCH v3 1/5] ASoC: Correct typo in SOC_VALUE_ENUM_SINGLE macro Lars-Peter Clausen
2015-05-04 12:03 ` Mark Brown
2015-05-04 14:23 ` Charles Keepax
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=20150506161637.GX22845@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=patches@opensource.wolfsonmicro.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 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.