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

    ASoC: tlv320aic32x4: Fix regmap range_min

to the 3.13-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-tlv320aic32x4-fix-regmap-range_min.patch
and it can be found in the queue-3.13 subdirectory.

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


>From e8e08c521dc101cf7e7e1caf4f487f9fe11a9a7a Mon Sep 17 00:00:00 2001
From: Markus Pargmann <[email protected]>
Date: Wed, 15 Jan 2014 18:12:40 +0100
Subject: ASoC: tlv320aic32x4: Fix regmap range_min

From: Markus Pargmann <[email protected]>

commit e8e08c521dc101cf7e7e1caf4f487f9fe11a9a7a upstream.

range_min is the lowest address in the virtual register range. This is
the first register with address 0, not the first register of page 1.

Currently all writes to page 1 are mapped to page 0, so the codec fails
to operate.

Fixes: 4d208ca429ad (ASoC: tlv320aic32x4: Convert to direct regmap API usage)
Signed-off-by: Markus Pargmann <[email protected]>
Signed-off-by: Mark Brown <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

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

--- a/sound/soc/codecs/tlv320aic32x4.c
+++ b/sound/soc/codecs/tlv320aic32x4.c
@@ -267,7 +267,7 @@ static const struct regmap_range_cfg aic
                .selector_mask  = 0xff,
                .window_start = 0,
                .window_len = 128,
-               .range_min = AIC32X4_PAGE1,
+               .range_min = 0,
                .range_max = AIC32X4_RMICPGAVOL,
        },
 };


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

queue-3.13/asoc-codec-tlv320aic32x4-fix-regmap-range-config.patch
queue-3.13/asoc-tlv320aic32x4-fix-regmap-range_min.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