rtc: fsl-ftm-alarm: avoid struct rtc_time conversions

Directly call ktime_get_real_seconds instead of converting the result to a
struct rtc_time and then back to a time64_t.

Link: https://lore.kernel.org/r/20191016201223.30568-4-alexandre.belloni@bootlin.com
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>

diff --git a/drivers/rtc/rtc-fsl-ftm-alarm.c b/drivers/rtc/rtc-fsl-ftm-alarm.c
index 039bd2f..9e6e994 100644 (file)
--- a/drivers/rtc/rtc-fsl-ftm-alarm.c
+++ b/drivers/rtc/rtc-fsl-ftm-alarm.c
@@ -203,17 +203,14 @@ static int ftm_rtc_read_alarm(struct device *dev, struct rtc_wkalrm *alm)
  */
 static int ftm_rtc_set_alarm(struct device *dev, struct rtc_wkalrm *alm)
 {
-       struct rtc_time tm;
-       time64_t now, alm_time;
+       time64_t alm_time;
        unsigned long long cycle;
        struct ftm_rtc *rtc = dev_get_drvdata(dev);
 
-       ftm_rtc_read_time(dev, &tm);
-       now = rtc_tm_to_time64(&tm);
        alm_time = rtc_tm_to_time64(&alm->time);
 
        ftm_clean_alarm(rtc);
-       cycle = (alm_time - now) * rtc->alarm_freq;
+       cycle = (alm_time - ktime_get_real_seconds()) * rtc->alarm_freq;
        if (cycle > MAX_COUNT_VAL) {
                pr_err("Out of alarm range {0~262} seconds.\n");
                return -ERANGE;