From 4ec57f14091c42e2f9502d1c17146a06fa105a88 Mon Sep 17 00:00:00 2001 From: Philip Chen Date: Mon, 21 May 2018 18:08:15 -0700 Subject: [PATCH] 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 Reviewed-on: https://chromium-review.googlesource.com/1068256 Commit-Ready: Martin Roth Tested-by: Philip Chen Tested-by: Martin Roth Reviewed-by: Martin Roth --- chip/stm32/clock-f.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/chip/stm32/clock-f.c b/chip/stm32/clock-f.c index 4b94c1f655..ee1c28dbb2 100644 --- a/chip/stm32/clock-f.c +++ b/chip/stm32/clock-f.c @@ -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);