linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v3] rtc: cros-ec: return -ETIME when refused to set alarms in the past
@ 2018-02-27  2:47 Jeffy Chen
  2018-02-27  2:53 ` JeffyChen
  0 siblings, 1 reply; 2+ messages in thread
From: Jeffy Chen @ 2018-02-27  2:47 UTC (permalink / raw)
  To: linux-kernel
  Cc: zyw, briannorris, dianders, jwerner, Jeffy Chen, linux-rtc,
	Alexandre Belloni, Alessandro Zummo

Since accessing a Chrome OS EC based rtc is a slow operation, there is a
race window where if the alarm is set for the next second and the second
ticks over right before calculating the alarm offset.

In this case the current driver is setting a 0-second alarm, which would
be considered as disabling alarms by the EC(EC_RTC_ALARM_CLEAR).

This breaks, e.g., hwclock which relies on RTC_UIE_ON ->
rtc_update_irq_enable(), which sets a 1-second alarm and expects it to
fire an interrupt.

So return -ETIME when the alarm is in the past, follow __rtc_set_alarm().

Signed-off-by: Jeffy Chen <jeffy.chen@rock-chips.com>
---

Changes in v3:
Fix alarm time comparing.

Changes in v2:
Rewrite commit message as Brian suggested.
Check alarm time only when that alarm is enabled.

 drivers/rtc/rtc-cros-ec.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/drivers/rtc/rtc-cros-ec.c b/drivers/rtc/rtc-cros-ec.c
index f0ea6899c731..510a4ced2edf 100644
--- a/drivers/rtc/rtc-cros-ec.c
+++ b/drivers/rtc/rtc-cros-ec.c
@@ -198,9 +198,9 @@ static int cros_ec_rtc_set_alarm(struct device *dev, struct rtc_wkalrm *alrm)
 	} else {
 		/* Don't set an alarm in the past. */
 		if ((u32)alarm_time < current_time)
-			alarm_offset = EC_RTC_ALARM_CLEAR;
-		else
-			alarm_offset = (u32)alarm_time - current_time;
+			return -ETIME;
+
+		alarm_offset = (u32)alarm_time - current_time;
 	}
 
 	ret = cros_ec_rtc_set(cros_ec, EC_CMD_RTC_SET_ALARM, alarm_offset);
-- 
2.11.0

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH v3] rtc: cros-ec: return -ETIME when refused to set alarms in the past
  2018-02-27  2:47 [PATCH v3] rtc: cros-ec: return -ETIME when refused to set alarms in the past Jeffy Chen
@ 2018-02-27  2:53 ` JeffyChen
  0 siblings, 0 replies; 2+ messages in thread
From: JeffyChen @ 2018-02-27  2:53 UTC (permalink / raw)
  To: Jeffy Chen, linux-kernel
  Cc: zyw, briannorris, dianders, jwerner, linux-rtc,
	Alexandre Belloni, Alessandro Zummo

Hi guys,

On 02/27/2018 10:47 AM, Jeffy Chen wrote:
>   		/* Don't set an alarm in the past. */
>   		if ((u32)alarm_time < current_time)
Oops, i'm a idiot, forgot to use '<='... will resend it.
> -			alarm_offset = EC_RTC_ALARM_CLEAR;
> -		else
> -			alarm_offset = (u32)alarm_time - current_time;
> +			return -ETIME;
> +
> +		alarm_offset = (u32)alarm_time - current_time;
>   	}

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-02-27  2:53 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-02-27  2:47 [PATCH v3] rtc: cros-ec: return -ETIME when refused to set alarms in the past Jeffy Chen
2018-02-27  2:53 ` JeffyChen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).