[PATCH] OMAP4 do not set TPS62361_REG_ADDR_SET0

[Nishanth Menon]

On Wed, Jun 12, 2013 at 2:17 AM, Jan Weitzel <j.weitzel at phytec.de> wrote:
> Don't set SET0 voltage, because it acts as boot voltage for OPP boot.
> Take care that the kernel doesn't drive vset gpio to low. This may
> happen while reseting the gpio module at initialization, look for
> HWMOD_INIT_NO_RESET.
>
> Signed-off-by: Jan Weitzel <j.weitzel at phytec.de>
> ---
>  arch/arm/mach-omap/omap4_generic.c |    5 ++---
>  1 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/mach-omap/omap4_generic.c b/arch/arm/mach-omap/omap4_generic.c
> index 7200393..bf1f1a7 100644
> --- a/arch/arm/mach-omap/omap4_generic.c
> +++ b/arch/arm/mach-omap/omap4_generic.c
> @@ -586,11 +586,10 @@ noinline int omap4460_scale_vcores(unsigned vsel0_pin, unsigned volt_mv)
>         writel(0x6026, OMAP44XX_PRM_VC_CFG_I2C_CLK);
>
>         /* TPS - supplies vdd_mpu on 4460
> -        * Setup SET1 and SET0 with right values so that kernel
> -        * can use either of them based on its needs.
> +        * Setup SET1 and don't touch SET0 it acts as boot voltage
> +        * source after reset.
>          */
>
> -       omap4_do_scale_tps62361(TPS62361_REG_ADDR_SET0, volt_mv);
>         omap4_do_scale_tps62361(TPS62361_REG_ADDR_SET1, volt_mv);
>
>         /*
> --
> 1.7.0.4
Reviewed-by: Nishanth Menon <nm at ti.com>