Philip Chen e2a9ede352 chip/stm32/clock: Handle illegal alarm timeout gracefully ...

Even if we set the rtc alarm timeout for more than 86400 secs,
we should not crash the system.

BUG=chromium:768042
BRANCH=none
TEST=on AP console, do 'ectool rtcsetalarm 99999' and
then see 'EC result 3 (INVALID_PARAM)' without crash.

Change-Id: Ic0fa92ff101bce1f4791221c4e1eadaf7a005355
Signed-off-by: Philip Chen <philipchen@google.com>
Reviewed-on: https://chromium-review.googlesource.com/807624
Commit-Ready: Philip Chen <philipchen@chromium.org>
Tested-by: Philip Chen <philipchen@chromium.org>
Reviewed-by: Shawn N <shawnn@chromium.org>

2017-12-06 17:30:47 -08:00

..

g

g:sps: do not stall reset when CS is asserted

2017-11-30 07:09:46 -08:00

host

Mark reset and panic functions as noreturn

2017-11-07 15:25:17 -08:00

ish

system: Allow hibernate to clear AP_OFF flag

2017-12-05 18:00:38 -08:00

it83xx

nds32: enable GCC LTO

2017-11-30 07:09:47 -08:00

lm4

host_events: Bump up host events and masks to 64-bit

2017-11-21 18:53:35 -08:00

mec1322

system: Allow hibernate to clear AP_OFF flag

2017-12-05 18:00:38 -08:00

npcx

system: Allow hibernate to clear AP_OFF flag

2017-12-05 18:00:38 -08:00

nrf51

cleanup: Remove jtag_pre_init()

2017-09-07 15:01:05 -07:00

stm32

chip/stm32/clock: Handle illegal alarm timeout gracefully

2017-12-06 17:30:47 -08:00