summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorLukasz Majewski <l.majewski@samsung.com>2013-10-31 16:52:55 +0100
committerChanho Park <chanho61.park@samsung.com>2014-11-18 11:45:02 +0900
commit7a009523165c53d74043b0e996937969808e1c50 (patch)
treec1dc7e70b408020e15e34c02b54441c6930f72dd /arch
parentcf4914accb7fcbb712d3ecddcf52a746d8334f08 (diff)
downloadlinux-3.10-7a009523165c53d74043b0e996937969808e1c50.tar.gz
linux-3.10-7a009523165c53d74043b0e996937969808e1c50.tar.bz2
linux-3.10-7a009523165c53d74043b0e996937969808e1c50.zip
regulator:max77686: Correct GPIOs for BUCK2 DVS setting
Before this patch SELB and DVS pins were wrongly defined in the DTS. As a result MAX77686 always used BUCK2_DVS1 register (the DVS pins were set all to 0). However the default DVS index (default_dvs_idx) was set to 1. Therefore, the default value of BUCK2_DVS1 register (1.1V) was always setup. Wrongly the driver was changing BUCK2_DVS2 register. Due to that voltage was NOT changed at all. The problem appeared when BOOST was ported to v3.10-mobile. It requires around 1.3V, but default voltage is set to 1.1V (0x28). Too small voltage resulted in OOPs at random places. As a side note: The MAX77686 is NOT using DVS with GPIO. It changes the value of current voltage with I2C utilization. Tested at: REDWOOD - Exynos4412 - rev1. Signed-off-by: Lukasz Majewski <l.majewski@samsung.com>
Diffstat (limited to 'arch')
-rw-r--r--arch/arm/boot/dts/exynos4412-slp_pq.dts4
1 files changed, 2 insertions, 2 deletions
diff --git a/arch/arm/boot/dts/exynos4412-slp_pq.dts b/arch/arm/boot/dts/exynos4412-slp_pq.dts
index 5c3beddd780..e05f3fa0c34 100644
--- a/arch/arm/boot/dts/exynos4412-slp_pq.dts
+++ b/arch/arm/boot/dts/exynos4412-slp_pq.dts
@@ -561,11 +561,11 @@
reg = <0x09>;
#clock-cells = <1>;
- max77686,dvs_gpios = <&gpf3 1 0>,
+ max77686,selb_gpios = <&gpf3 1 0>,
<&gpf3 2 0>,
<&gpf3 3 0>;
- max77686,selb_gpios = <&gpm3 0 0>,
+ max77686,dvs_gpios = <&gpm3 0 0>,
<&gpm3 1 0>,
<&gpm3 2 0>;