On 04/12/2020 10:08:19-0400, Jason Gunthorpe wrote: > On Fri, Dec 04, 2020 at 02:02:57PM +0100, Thomas Gleixner wrote: > > > No magic sign calculation required if you look at it from the actual > > timeline and account the time between write and next second increment > > correctly. > > Yes, it is equivalent to break things into two values, and does look > to be more understandable as one can read at least one of the values > from a datasheet and the other could be estimated by timing a read > clock > If you want to read an RTC accurately, you don't want to time a read, what you want is to time an alarm. This is a common misconception and is, again, why hctosys in its current state is not useful. And because people using systohc are definitively using hctosys, this will still result in an up to 500ms error in the current time. As said, the price to pay for a proper solution will be an up to one second delay when booting which is not acceptable for most users. Is "fixing" systohc worth the effort and the maintenance cost? -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
