From: Tyler Hicks <code@tyhicks.com>
To: Meagan Lloyd <meaganlloyd@linux.microsoft.com>,
alexandre.belloni@bootlin.com,
Rodolfo Giometti <giometti@enneenne.com>
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Expand oscillator stop flag (OSF) validity check to ds1341
Date: Mon, 30 Jun 2025 17:54:45 -0500 [thread overview]
Message-ID: <aGMVtfwB5gmBuW4T@redbud> (raw)
In-Reply-To: <1749665656-30108-1-git-send-email-meaganlloyd@linux.microsoft.com>
[Adding Rodolfo Giometti]
On 2025-06-11 11:14:14, Meagan Lloyd wrote:
> We would like to use CONFIG_RTC_HCTOSYS to sync a supercapacitor-backed
> DS1342 RTC to the kernel time early in boot. An obstacle is that the
> sync in rtc_hctosys() is unconditional as long as rtc_read_time()
> succeeds and in some power loss situations, our RTC comes up with either
> an unpredictable future time or the default 01/01/00 from the datasheet.
> Syncing a future time, followed by an NTP sync would not be desired as
> it would result in a backwards time jump. The sync feature is useful in
> boot scenarios where power is maintained so syncing only when the RTC
> data is valid would allow us to make use of the feature.
>
> The DS1342 has the oscillator stop flag (OSF) which is a status flag
> indicating that the oscillator stopped for a period of time. It can be
> set due to power loss. Some chip types in the ds1307 driver already use
> the OSF to determine whether .read_time should provide valid data or
> return -EINVAL. This patch series expands that handling to the ds1341
> chip type (DS1341 and DS1342 share a datasheet).
>
> These changes enable us to make use of CONFIG_RTC_HCTOSYS as they
> prevent the invalid time from getting synced to the kernel time. It will
> also prevent userspace programs from getting the invalid time as the fix
> cuts it off at the source - the .read_time function.
These two patches look good to me, although I'm not an expert in RTC drivers.
I've reviewed the DS1341/DS1342 datasheet and the approach that Meagan has
taken makes sense to me given our (Meagan and I work together) desire to use
CONFIG_RTC_HCTOSYS and the need to avoid syncing from an invalid RTC state.
I've added Rodolfo because he first added the logic to clear the Oscillator
Stop Flag, during driver initialization, way back in 2007 with v2.6.23 commit
be5f59f4b67f ("rtc-ds1307: oscillator restart for ds13{37,38,39,40}") and may
have additional context to provide.
Alexandre and Rodolfo, does this approach make sense to you? If not, do you
have any other suggestions on how to make CONFIG_RTC_HCTOSYS work with this
driver? Thanks!
Tyler
>
> Meagan Lloyd (2):
> rtc: ds1307: remove clear of oscillator stop flag (OSF) in probe
> rtc: ds1307: handle oscillator stop flag (OSF) for ds1341
>
> drivers/rtc/rtc-ds1307.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
>
> base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-06-30 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 18:14 [PATCH 0/2] Expand oscillator stop flag (OSF) validity check to ds1341 Meagan Lloyd
2025-06-11 18:14 ` [PATCH 1/2] rtc: ds1307: remove clear of oscillator stop flag (OSF) in probe Meagan Lloyd
2025-06-11 18:14 ` [PATCH 2/2] rtc: ds1307: handle oscillator stop flag (OSF) for ds1341 Meagan Lloyd
2025-06-30 22:54 ` Tyler Hicks [this message]
2025-07-02 14:37 ` [PATCH 0/2] Expand oscillator stop flag (OSF) validity check to ds1341 Rodolfo Giometti
2025-07-02 14:52 ` Tyler Hicks
2025-07-23 21:25 ` Alexandre Belloni
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=aGMVtfwB5gmBuW4T@redbud \
--to=code@tyhicks.com \
--cc=alexandre.belloni@bootlin.com \
--cc=giometti@enneenne.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=meaganlloyd@linux.microsoft.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox