Wonjoon Lee da5b8fa6c7 Wait for battery boot-up ...

Some battery uses clock stretching feature, and this could disturb
PMU communication before battery going stable.
AP does not know and will attempt PMU setting, and could get fail
For various battery indicates usually 1s for stable
(even if it is much less in real world 200ms~700ms)
Let's checking 'battery is ready' when first pump-up power.

BUG=chrome-os-partner:28289
TEST=Going battery shipmode and plug-in AC, See booting and EC log
Disconnect battery, and plug-in and see booting and EC log

Change-Id: I9b62266132d5322366265afe03adbe0db1f9ae75
Signed-off-by: Wonjoon Lee <woojoo.lee@samsung.com>
Reviewed-on: https://chromium-review.googlesource.com/197991
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Tested-by: Doug Anderson <dianders@chromium.org>

2014-05-08 08:35:41 +00:00

..

baytrail.c

baytrail: Workaround for stuck boot process

2014-04-30 10:00:02 +00:00

build.mk

x86 & tegra: add CONFIG_POWER_COMMON.

2014-01-21 01:13:15 +00:00

common.c

nyan: fix the power in_signals out of sync bug.

2014-05-06 00:08:13 +00:00

gaia.c

Wait for battery boot-up

2014-05-08 08:35:41 +00:00

haswell.c

Allow AP to set wireless power state in suspend

2014-02-22 00:50:37 +00:00

ivybridge.c

Allow AP to set wireless power state in suspend

2014-02-22 00:50:37 +00:00

tegra.c

tegra: keeps AP in off state for "reboot ap-off"

2014-05-03 02:11:36 +00:00