Vic Yang eab146be79 stm32f3: Use the correct RTC ALARM IRQ ...

On STM32F0, a single IRQ is used for all RTC events, including RTC_ALARM
and RTC_WAKEUP, and this IRQ is named RTC_WAKEUP. We use RTC_WAKEUP IRQ
in our code while we actually meant to capture RTC alarm event. On
STM32F3, RTC_WAKEUP and RTC_ALARM are separate IRQs and thus we're
having problem. Let's make it explicit which RTC IRQ we want to use and
fix our code to use RTC_ALARM.

BRANCH=None
BUG=chrome-os-partner:33219
TEST=Run 'rtc_alarm' on Ryu and verify the EC gets interrupted after a
second.

Change-Id: Ib1a14a5da49d709a4d071d44fbfa46544cc5929b
Signed-off-by: Vic Yang <victoryang@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/224998
Reviewed-by: Alec Berg <alecaberg@chromium.org>
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>

2014-10-23 03:32:51 +00:00

..

host

Fix incorrect valid and writable flash flags

2014-10-15 23:56:27 +00:00

it83xx

watchdog: Give more leeway to the independent watchdog

2014-06-23 21:48:42 +00:00

lm4

samus: change fan RPM values, enable fast-start

2014-10-22 02:23:39 +00:00

mec1322

mec1322: Simplify reading raw I2C pin states

2014-07-09 20:29:55 +00:00

nrf51

hadoken: initial commit.

2014-07-29 02:21:22 +00:00

stm32

stm32f3: Use the correct RTC ALARM IRQ

2014-10-23 03:32:51 +00:00