summaryrefslogtreecommitdiffstats
path: root/arch
diff options
context:
space:
mode:
authorOtavio Salvador <otavio@ossystems.com.br>2012-08-05 09:05:33 +0000
committerAlbert ARIBAUD <albert.u.boot@aribaud.net>2012-09-01 14:58:17 +0200
commit05c823bd327e39586067262c25148cb4888974ab (patch)
treee9e27671756192069b38d0671bf296110bbbf854 /arch
parent1e0cf5c34bd3074d6b026035354a89121fbf224f (diff)
downloadblackbird-obmc-uboot-05c823bd327e39586067262c25148cb4888974ab.tar.gz
blackbird-obmc-uboot-05c823bd327e39586067262c25148cb4888974ab.zip
mxs: Clarify why we poweroff in case of brownout in 5v conflict
If VDDIO has a brownout, then the VDD5V_GT_VDDIO becomes unreliable but this wasn't clear on code so a comment has been added to clarify it. Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Diffstat (limited to 'arch')
-rw-r--r--arch/arm/cpu/arm926ejs/mxs/spl_power_init.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/arch/arm/cpu/arm926ejs/mxs/spl_power_init.c b/arch/arm/cpu/arm926ejs/mxs/spl_power_init.c
index c341960f38..6dd3bfc9bc 100644
--- a/arch/arm/cpu/arm926ejs/mxs/spl_power_init.c
+++ b/arch/arm/cpu/arm926ejs/mxs/spl_power_init.c
@@ -577,6 +577,10 @@ void mxs_handle_5v_conflict(void)
tmp = readl(&power_regs->hw_power_sts);
if (tmp & POWER_STS_VDDIO_BO) {
+ /*
+ * VDDIO has a brownout, then the VDD5V_GT_VDDIO becomes
+ * unreliable
+ */
mxs_powerdown();
break;
}
OpenPOWER on IntegriCloud