Re: [PATCH v9 0/4] virtio-rtc: Add device specification
Peter Hilber <[email protected]>
| Newsgroups | dev.linux.lists.virtio-comment |
|---|---|
| Message-ID | <ijqnvwvqcrzcn3dq6uz46u2ptw7idjjsthl3xjz4btzhoc5oao@xhqpjbcl7ue5> |
On Wed, May 07, 2025 at 05:50:32PM +0200, Peter Hilber wrote: > This iteration of the spec should address multiple review findings from > Cornelia Huck, Matias Ezequiel Vara Larsen, and Michael S. Tsirkin. > > Summary > ------- > > The RTC (Real Time Clock) device provides information about current > time. The device can provide different clocks, for the UTC or TAI time > standards, or for physical time elapsed since some past epoch. For UTC > clocks, the device can also indicate how leap seconds are handled. The > driver can read the clocks with simple or more accurate methods. > Optionally, the driver can set an alarm. > > The driver-side timekeeping can synchronize precisely to a local clock > exposed by the RTC device. If supported by the device, the driver can > obtain a cross-timestamp from the local clock and the system hardware > counter, in a way similar to the Linux kernel ptp_kvm driver [1]. > > The alarm allows the driver side to be woken up from a sleep state at a > specific time. > Could you please open a voting ballot for these changes? Fixes: https://github.com/oasis-tcs/virtio-spec/issues/221 This version of the patch series should have addressed all issues raised so far. Since posting it 4 weeks ago, there has been no additional feedback. I updated the Github issue to point to v9 instead of v8. Best regards, Peter