diff options
| author | Nishanth Menon <nm@ti.com> | 2012-03-01 14:17:38 +0000 |
|---|---|---|
| committer | Albert ARIBAUD <albert.u.boot@aribaud.net> | 2012-05-15 08:31:22 +0200 |
| commit | 3acb553439e3ee9f62f022f96f949c21811f8bdf (patch) | |
| tree | 769d474b7aa9976bf1835938eafdac7d15fd090c /common/menu.c | |
| parent | a78274b2050dcacc29561f4e35bdc91b896578cd (diff) | |
| download | u-boot-imx-3acb553439e3ee9f62f022f96f949c21811f8bdf.zip u-boot-imx-3acb553439e3ee9f62f022f96f949c21811f8bdf.tar.gz u-boot-imx-3acb553439e3ee9f62f022f96f949c21811f8bdf.tar.bz2 | |
OMAP4460: TPS Ensure SET1 is selected after voltage configuration
TPS SET0/SET1 register is selected by a GPIO pin on OMAP4460 platforms.
Currently we control this pin with a mux configuration as part of
boot sequence.
Current configuration results in the following voltage waveform:
|---------------| (SET1 default 1.4V)
| --------(programmed voltage)
| <- (This switch happens on mux7,pullup)
vdd_mpu(TPS) -----/ (OPP boot voltage)
--------- (programmed voltage)
vdd_core(TWL6030) -----------------------/ (OPP boot voltage)
Problem 1) |<----- Tx ------>|
timing violation for a duration Tx close to few milliseconds.
Problem 2) voltage of MPU goes beyond spec for even the highest of MPU OPP.
By using GPIO as recommended as standard procedure by TI, the sequence
changes to:
-------- (programmed voltage)
vdd_mpu(TPS) ------------/ (Opp boot voltage)
--------- (programmed voltage)
vdd_core(TWL6030) -------------/ (OPP boot voltage)
NOTE: This does not attempt to address OMAP5 - Aneesh please confirm
Reported-by: Isabelle Gros <i-gros@ti.com>
Reported-by: Jerome Angeloni <j-angeloni@ti.com>
Signed-off-by: Nishanth Menon <nm@ti.com>
Diffstat (limited to 'common/menu.c')
0 files changed, 0 insertions, 0 deletions