chip/stm32/clock: Initialize 'alarm_us'

The new GCC build shows a warning/error in clock-f.c:

'alarm_us' may be used uninitialized in this function
[-Werror=maybe-uninitialized]

This is actually a fake warning. In the context of the logic,
there is no way 'alarm_us' would be used uninitialized.

But let's still initialize 'alarm_us' to clear the compiler warning.

BUG=none
BRANCH=scarlet
TEST='USE=coreboot-sdk emerge-scarlet chromeos-ec'
TEST=make buildall -j

Change-Id: I7a0642cbe03c5a0adb6997ddc80c9cb797715749
Signed-off-by: Philip Chen <philipchen@google.com>
Reviewed-on: https://chromium-review.googlesource.com/1068256
Commit-Ready: Martin Roth <martinroth@chromium.org>
Tested-by: Philip Chen <philipchen@chromium.org>
Tested-by: Martin Roth <martinroth@chromium.org>
Reviewed-by: Martin Roth <martinroth@chromium.org>
This commit is contained in:
Philip Chen
2018-05-21 18:08:15 -07:00
committed by chrome-bot
parent 038e75cd85
commit 4ec57f1409

View File

@@ -165,7 +165,8 @@ void rtc_read(struct rtc_time_reg *rtc)
void set_rtc_alarm(uint32_t delay_s, uint32_t delay_us,
struct rtc_time_reg *rtc)
{
uint32_t alarm_sec, alarm_us;
uint32_t alarm_sec = 0;
uint32_t alarm_us = 0;
if (delay_s == EC_RTC_ALARM_CLEAR && !delay_us) {
reset_rtc_alarm(rtc);