All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: "Csókás, Bence" <csokas.bence@prolan.hu>
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH resubmit] rtc: interface: Add RTC offset to alarm after fix-up
Date: Wed, 19 Jun 2024 15:26:38 +0200	[thread overview]
Message-ID: <20240619132638b08dcc9d@mail.local> (raw)
In-Reply-To: <20240619130115.2799118-1-csokas.bence@prolan.hu>

On 19/06/2024 15:01:16+0200, Csókás, Bence wrote:
> `rtc_add_offset()` is called by `__rtc_read_time()`
> and `__rtc_read_alarm()` to add the RTC's offset to
> the raw read-outs from the device drivers. However,
> in the latter case, a fix-up algorithm is run if
> the RTC device does not report a full `struct rtc_time`
> alarm value. In that case, the offset was forgot to be
> added.
> 
> Fixes: fd6792bb022e ("rtc: fix alarm read and set offset")
> 
> Signed-off-by: Csókás, Bence <csokas.bence@prolan.hu>
> ---
>  drivers/rtc/interface.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/rtc/interface.c b/drivers/rtc/interface.c
> index 1b63111cdda2..db8dffffed91 100644
> --- a/drivers/rtc/interface.c
> +++ b/drivers/rtc/interface.c
> @@ -273,12 +273,11 @@ int __rtc_read_alarm(struct rtc_device *rtc, struct rtc_wkalrm *alarm)
>  		if (err)
>  			return err;
>  
>  		/* full-function RTCs won't have such missing fields */
>  		if (rtc_valid_tm(&alarm->time) == 0) {
> -			rtc_add_offset(rtc, &alarm->time);
> -			return 0;
> +			goto done;
>  		}
>  
>  		/* get the "after" timestamp, to detect wrapped fields */
>  		err = rtc_read_time(rtc, &now);
>  		if (err < 0)
> @@ -378,10 +377,12 @@ int __rtc_read_alarm(struct rtc_device *rtc, struct rtc_wkalrm *alarm)
>  done:
>  	if (err && alarm->enabled)
>  		dev_warn(&rtc->dev, "invalid alarm value: %ptR\n",
>  			 &alarm->time);
>  
> +	rtc_add_offset(rtc, &alarm->time);
> +

This must not be done when the tm is invalid.

>  	return err;
>  }
>  
>  int rtc_read_alarm(struct rtc_device *rtc, struct rtc_wkalrm *alarm)
>  {
> -- 
> 2.34.1
> 
> 

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2024-06-19 13:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 13:01 [PATCH resubmit] rtc: interface: Add RTC offset to alarm after fix-up Csókás, Bence
2024-06-19 13:26 ` Alexandre Belloni [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240619132638b08dcc9d@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=csokas.bence@prolan.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.