ARM: dts: OMAP3: add voltage controller nodes

OMAP3 family of SoCs (3430/3530/3630/3730..) use same offsets for
voltage controller and the same IP block.

Introduce the voltage controller nodes for the same with their
different voltage characteristics.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: OMAP3: add voltage processor nodes

OMAP3 family of SoCs (3430/3530/3630/3730..) use same offsets for
voltage processor and the same IP block.

Introduce the voltage processor nodes for the same with their
different voltage characteristics.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: OMAP4: add voltage controller nodes

OMAP443x, OMAP446x SoC use same offsets for voltage controller,
however their voltage characteristics differ a little.

Introduce the voltage controller nodes for the same.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: OMAP4: add voltage processor nodes

OMAP443x, OMAP446x SoC use same offsets for voltage processor,
however their voltage characteristics differ a little.

Introduce the voltage processor nodes for the same.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: OMAP5: add voltage controller nodes

OMAP5430/5432 SoC use same offsets for voltage controller,
however their voltage characteristics differ a little.

NOTE: DRA7 variants of OMAP5 do not contain Voltage Controller

Introduce the voltage controller nodes for the same.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: OMAP5: add voltage processor nodes

OMAP5430/5432 SoC use same offsets for voltage processor,
however their voltage characteristics differ a little.

NOTE: DRA7 variants of OMAP5 do not contain Voltage
Processor

Introduce the voltage Processor nodes for the same.

Signed-off-by: Nishanth Menon <nm@ti.com>
mfd: twl-core: allow enable SR path for TWL4030 family

TWL4030 family of Power Management ICs(PMIC) allow control of PMIC's
VDD1,2 supplies using either I2C1 (regular control I2C path) OR over
I2C_SR (dedicated SR path for communication with dedicated hardware
I2C controllers such as OMAP's Voltage Controller(VC) interface)

However only one path can be active at any given time. Hence, allow
this to be selected using device tree node description.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: twl4030_omap3: Link OMAP voltage path to TWL4030

Associate TWl4030 VDD1 for VDD_MPU and VDD2 to VDD_CORE using
corresponding VP path. and use highspeed mode for communication
from Voltage Controller to TWL4030.

Signed-off-by: Nishanth Menon <nm@ti.com>
regulator: twl-regulator: allow for setting voltage offset where allowed.

In TWL603[02] depending on the value of SMPS_OFFSET efuse register
the voltage range supported in standard mode can be either
between 0.6V - 1.3V or 0.7V - 1.4V.

However the same chip can be produced with differing internal firmware
which may or may not allow for offset to be reprogrammed on the device.
Handle this on the fly and provide device tree bindings for the same.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: twl6030/omap4: Add OMAP voltage path linkage

OMAP4430 and 4460 platforms use TWL6030 to power voltage rails.
However, on 4460, we use twl6030 only for iva and core voltage rails.

Introduce an twl6030_omap4.dtsi to be able to reuse the base definition
for all OMAP4 platforms and the delta change only for panda-es platform
which is based on 4460.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: omap4-panda-es: add TPS62361 supply for vdd_mpu

Unlike other OMAP4 platforms including the the "vanilla" PandaBoard,
PandaBoard-ES uses TPS62361 to supply vdd_mpu.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: omap4-panda-es: use tps regulator as cpu0 supply

TPS62361 is used for cpufreq regulation on PandaBoard-ES platform. As
part of this change use labels that can be used to reference cpu0 to
setup it's supply.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: twl6030_omap4: use vcore1 regulator as cpu0 supply

All platforms other than PandaBoard-ES uses VCORE1 for cpufreq
regulation. Since we have introduced appropriate change needed for
PandaBoard-ES platform, we now setup twl6030_vcore1 as CPU supply for
remaining OMAP4 platforms using TWL6030 on OMAP4.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: omap5-uevm: document regulator names used on the actual board

commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.

However, currently we use the Palmas regulator names which is used for
different purposes on uEVM. Document the same based on 750-2628-XXX
boards - which use OMAP5432 ES2.0 meant for production and the
platform meant to be supported by this dts.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: omap5-uevm: remove always-on for LDOs supplying J19 connector

commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.

However, J19 connector has the following supplies hooked to it
ldoln(VDD_2v1), ldo6(VDDS_1V2_MAIN), VDD_2v1(VDDA_1v8_REF)

None of these supplies need to be always powered on without ability to
disable.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: omap5-uevm: reduce LDO1 voltage to 1.5V

commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.

However, LDO1 supplies VDDAPHY_CAM which is OMAP5's vdda_csiporta/b/c.

This can only be supplied at 1.5V or 1.8V and we currently supply 2.8V.

To prevent potential risk, use the specified 1.5V-1.8V supply.

TBD: does this need to be always-on? to be clarified with h/w team.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: omap5-uevm: reduce LDO4 voltage to 1.5V

commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.

However, LDO4 supplies VDDAPHY_DISP which is vdda_dsiporta/c/vdda_hdmi

This can only be supplied at 1.5V or 1.8V and we currently
supply 2.2V.

To prevent potential risk, use the specified 1.5V-1.8V supply.

TBD: does this need to be always-on? to be clarified
with h/w team.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: omap5-uevm: reduce LDO6 voltage to 1.2V

commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.

However, LDO6 supplies the board specified VDDS_1V2_MAIN supply going to J19
connector. To stay within the board specification supply 1.2V instead
of 1.5V.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: omap5-uevm: increase LDO7 voltage to 2V and disable it

commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.

However, LDO4 supplies VDD_VPP which is vpp1. This is currently configured for
1.5V which as per data manual "A pulse width of 1000 ns and an amplitude
of 2V is required to program each eFuse bit. Otherwise, VPP1 must not
be supplied".

So, fix the voltage to 2V. and disable the supply since we have no plans
of programming efuse bits - it can only be done once - in factory.

Signed-off-by: Nishanth Menon <nm@ti.com>
ARM: dts: omap5-uevm: increase LDO8 voltage to 3V

commit e00c27ef3b4c23e39d0a77b7c8e5be44c28001c7
(ARM: dts: OMAP5: Add Palmas MFD node and regulator nodes)
introduced regulator entries for OMAP5uEVM.

However, LDO8 supplies the board specified VDD_3v0 supply going to XYZ
connector. To stay within the board specification supply 3V
instead of 1.5V.

TBD - if it is going to a connector - auto disable this as well.

Signed-off-by: Nishanth Menon <nm@ti.com>