From: Thomas Gleixner <tglx@linutronix.de>
To: John Stultz <john.stultz@linaro.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: Joel Daniels <jdaniels@sent.com>, Stephen Boyd <sboyd@kernel.org>,
linux-kernel@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>,
linux-rtc@vger.kernel.org, x86@kernel.org
Subject: Re: Time keeping while suspended in the presence of persistent clock drift
Date: Wed, 15 Dec 2021 23:33:10 +0100 [thread overview]
Message-ID: <87pmpxlcrd.ffs@tglx> (raw)
In-Reply-To: <CALAqxLWe13ZghdWphzWZZsRGa+MeAH58syfem6ktDFHF0WG4Dg@mail.gmail.com>
On Wed, Dec 15 2021 at 14:02, John Stultz wrote:
> On Wed, Dec 15, 2021 at 1:32 PM Alexandre Belloni
>> I'd rather lean towards the timekeeping code doing that. The RTC
>
> Heh, touche'! :)
>
>> subsystem doesn't know which RTC has to be used.
>
> Though the RTC layer *is* the one that tracks which RTC is used, via
> the logic in drivers/rtc/class.c, and the timekeeping core already has
> adjtimex for timekeeping corrections, so if we're correcting
> underlying RTCs it seems such tuning would best be done in the RTC
> layer.
>
> Though how the persistent_clock interface ties into such corrections
> would be a separate thing.
Might be the final trigger to get rid of that leftover from the last
millenium?
Thanks,
tglx
next prev parent reply other threads:[~2021-12-15 22:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 17:55 Time keeping while suspended in the presence of persistent clock drift Joel Daniels
2021-12-09 18:06 ` Joel Daniels
2021-12-11 13:36 ` Thomas Gleixner
2021-12-13 13:39 ` Joel Daniels
2021-12-14 13:57 ` Thomas Gleixner
2021-12-14 17:43 ` Joel Daniels
2021-12-15 21:06 ` John Stultz
2021-12-15 21:32 ` Alexandre Belloni
2021-12-15 22:02 ` John Stultz
2021-12-15 22:33 ` Thomas Gleixner [this message]
2021-12-15 23:10 ` John Stultz
2021-12-15 22:42 ` Joel Daniels
2021-12-15 23:26 ` John Stultz
2021-12-15 23:36 ` Alexandre Belloni
2021-12-16 0:09 ` Joel Daniels
2021-12-15 23:28 ` Alexandre Belloni
2021-12-15 21:42 ` Alexandre Belloni
2021-12-15 22:05 ` Joel Daniels
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=87pmpxlcrd.ffs@tglx \
--to=tglx@linutronix.de \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=jdaniels@sent.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox