summaryrefslogtreecommitdiffstats
path: root/board/lg/sniper
diff options
context:
space:
mode:
authorPaul Kocialkowski <contact@paulk.fr>2016-03-29 14:16:25 +0200
committerTom Rini <trini@konsulko.com>2016-04-01 17:18:06 -0400
commitc15ab5be8ff3d07b1afafac9f1e79b3e37ab8624 (patch)
tree3211c42642de46a2805c25cb5edf353d0fb8229b /board/lg/sniper
parent44b0cf46c1bb37bb5df7bd93cb0efa3696df78fd (diff)
downloadblackbird-obmc-uboot-c15ab5be8ff3d07b1afafac9f1e79b3e37ab8624.tar.gz
blackbird-obmc-uboot-c15ab5be8ff3d07b1afafac9f1e79b3e37ab8624.zip
sniper: Proper reboot mode and boot reason validation
With the previous implementation, rebooting without registering a recognized reboot mode (despite registering the magic) would end up with U-Boot checking for a valid power-on reason, which might result in the device turning off (e.g. with no USB cable attached and no buttons pressed). This was designed to catch reboots that are actually intended to be power-off, something that old Android kernels do, instead of properly turning the device off using the TWL4030. However, since this approach is not viable (breaks reboot in most cases), the validity of the reboot mode magic is checked to detect a reboot and the 'o' char is recognized to indicate that power-off is required. Still, that might be overridden by the detection of usual power-on reasons, on purpose. Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
Diffstat (limited to 'board/lg/sniper')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud