| Re: [chrony-dev] [PATCH v1] rtc: handle uninitialized RTC |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] [PATCH v1] rtc: handle uninitialized RTC
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 1 Jul 2024 09:44:53 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1719819899; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=N6bquHSUbcq9NXq0Mams3k7cdnGu911ksg0xbs20vSQ=; b=ApStDv1SMh6dDQwpqGWDR5lPnUO2LjG9imJwYOQePL3SYeRhCtSrCgutSFtSBOWcYVRd3c ugGfSm6jdnaRTphrXXhRSHokCOI/tBV0TD/vR/476LPvgAtVWCVhyElQ0Z+Irbhpl7Ne4K Q9zRS383tGn/xXWn36//dEpgukgEF3k=
On Sun, Jun 30, 2024 at 05:04:00PM +0200, Johannes Schneider wrote:
> Add a configuration option for an "initialization year/timestamp"
> chornyd can use to start an uninitialized RTC, so that the RTC driver
> can continue its start up, and chrony could later trim the RTC to an
> accurate date.
>
> Without this 'kick-off', on systems where the RTC would return -EINVAL
> when being queried either for features, or just being read, chronyd
> would be unable to start the RTC driver ("513 RTC driver not running")
> and hence could/would not set it.
>
> An example RTC where this is the case is RX8130 (of the ds1307
> family), which would return -EINVAL *until* the internal oscillator is
> started by writing a valid date to it.
Wouldn't all applications reading RTC need this patch? I think this
should be addressed in the kernel driver instead. Was there a
discussion about that?
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.