This is a note to let you know that I've just added the patch titled

    ASoC: Mark WM5100 register map cache only when going into BIAS_OFF

to the 3.2-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     asoc-mark-wm5100-register-map-cache-only-when-going-into-bias_off.patch
and it can be found in the queue-3.2 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From e53e417331c57b9b97e3f8be870214a02c99265c Mon Sep 17 00:00:00 2001
From: Mark Brown <[email protected]>
Date: Wed, 18 Jan 2012 20:02:38 +0000
Subject: ASoC: Mark WM5100 register map cache only when going into BIAS_OFF

From: Mark Brown <[email protected]>

commit e53e417331c57b9b97e3f8be870214a02c99265c upstream.

Writing to the registers won't work if we do actually manage to hit a fully
powered off state.

Signed-off-by: Mark Brown <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 sound/soc/codecs/wm5100.c |    1 +
 1 file changed, 1 insertion(+)

--- a/sound/soc/codecs/wm5100.c
+++ b/sound/soc/codecs/wm5100.c
@@ -1404,6 +1404,7 @@ static int wm5100_set_bias_level(struct
                break;
 
        case SND_SOC_BIAS_OFF:
+               regcache_cache_only(wm5100->regmap, true);
                if (wm5100->pdata.ldo_ena)
                        gpio_set_value_cansleep(wm5100->pdata.ldo_ena, 0);
                regulator_bulk_disable(ARRAY_SIZE(wm5100->core_supplies),


Patches currently in stable-queue which might be from 
[email protected] are

queue-3.2/asoc-wm8996-call-_post_pmu-callback-for-cpvdd.patch
queue-3.2/asoc-disable-register-synchronisation-for-low-frequency-wm8996-sysclk.patch
queue-3.2/asoc-mark-wm5100-register-map-cache-only-when-going-into-bias_off.patch
queue-3.2/asoc-don-t-go-through-cache-when-applying-wm5100-rev-a-updates.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to