From 535b4393623ca1208f60312693f52e9cfd070de9 Mon Sep 17 00:00:00 2001
From: Kevin Bracey <kevin.bracey@arm.com>
Date: Fri, 21 Dec 2018 13:12:34 +0200
Subject: [PATCH] Revert "STM32 RTC : skip rtc_write if possible"

`rtc_write` must start the RTC. `time()` uses `rtc_write(0)` to start
the RTC if it is not already enabled, but this check made that not
work.

There's no point trying to optimise this case in a HAL - if we wanted
`set_time()` to protect against users making pointless adjustments, the
implementation should be there. But even then, you might want different
levels of hysteresis depending on application, so it's probably best
left to applications.

This reverts commit 9da5e489418aba9d99c666edd9c55aad1d2ac2bc.
---
 targets/TARGET_STM/rtc_api.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/targets/TARGET_STM/rtc_api.c b/targets/TARGET_STM/rtc_api.c
index 8c2432b925..e28a311b84 100644
--- a/targets/TARGET_STM/rtc_api.c
+++ b/targets/TARGET_STM/rtc_api.c
@@ -217,11 +217,6 @@ void rtc_write(time_t t)
     RTC_DateTypeDef dateStruct = {0};
     RTC_TimeTypeDef timeStruct = {0};
 
-    /* if the requested time is the current time, no need to continue */
-    if (t == rtc_read()) {
-        return;
-    }
-
     core_util_critical_section_enter();
     RtcHandle.Instance = RTC;