From: Peter Hilber <peter.hilber@opensynergy.com>
To: virtio-comment@lists.oasis-open.org
Cc: Peter Hilber <peter.hilber@opensynergy.com>,
Cornelia Huck <cohuck@redhat.com>,
Parav Pandit <parav@nvidia.com>
Subject: [virtio-comment] [RFC PATCH v3 0/4] virtio-rtc: Add device specification
Date: Mon, 18 Dec 2023 07:42:49 +0100 [thread overview]
Message-ID: <20231218064253.9734-1-peter.hilber@opensynergy.com> (raw)
This iteration of the virtio-rtc RFC spec
- addresses the comments from Parav (patch 1),
- separates the normative statements into a dedicated patch (patch 2), and
- adds an optional alarm feature (patch 3-4).
Summary
-------
The RTC (Real Time Clock) device provides information about current
time. The device can provide different clocks, e.g. for the UTC or TAI
time standards, or for physical time elapsed since some past epoch. The
driver can read the clocks with simple or more accurate methods.
Optionally, the driver can set an alarm.
Changelog
---------
v3:
- Address comments from Parav Pandit.
- Add an optional alarm feature.
- Various other changes.
v2:
- Address comments from Cornelia Huck.
Peter Hilber (4):
virtio-rtc: Add initial device specification
virtio-rtc: Add initial normative statements
virtio-rtc: Add alarm feature
virtio-rtc: Add normative statements for alarm feature
conformance.tex | 2 +
content.tex | 3 +-
device-types/rtc/description.tex | 937 ++++++++++++++++++++++++
device-types/rtc/device-conformance.tex | 13 +
device-types/rtc/driver-conformance.tex | 11 +
5 files changed, 965 insertions(+), 1 deletion(-)
create mode 100644 device-types/rtc/description.tex
create mode 100644 device-types/rtc/device-conformance.tex
create mode 100644 device-types/rtc/driver-conformance.tex
base-commit: 4cb03b12dc951f0152cd2cd9c79b24492e174e43
--
2.40.1
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next reply other threads:[~2023-12-18 6:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 6:42 Peter Hilber [this message]
2023-12-18 6:42 ` [virtio-comment] [RFC PATCH v3 1/4] virtio-rtc: Add initial device specification Peter Hilber
2024-01-20 10:07 ` [virtio-comment] " Parav Pandit
2024-01-24 15:39 ` [virtio-comment] " Peter Hilber
2024-01-28 6:15 ` [virtio-comment] " Parav Pandit
2024-02-08 11:57 ` Peter Hilber
2024-02-09 11:43 ` Cornelia Huck
2023-12-18 6:42 ` [virtio-comment] [RFC PATCH v3 2/4] virtio-rtc: Add initial normative statements Peter Hilber
2023-12-18 6:42 ` [virtio-comment] [RFC PATCH v3 3/4] virtio-rtc: Add alarm feature Peter Hilber
2023-12-22 18:57 ` Cornelia Huck
2023-12-25 4:18 ` Jason Wang
2024-01-11 11:43 ` Peter Hilber
2024-01-11 11:43 ` Peter Hilber
2024-01-15 15:54 ` Cornelia Huck
2024-01-16 11:06 ` Peter Hilber
2024-01-20 10:16 ` [virtio-comment] " Parav Pandit
2024-01-24 15:40 ` [virtio-comment] " Peter Hilber
2024-01-28 6:30 ` [virtio-comment] " Parav Pandit
2024-01-29 16:51 ` Cornelia Huck
2024-02-01 5:53 ` Parav Pandit
2023-12-18 6:42 ` [virtio-comment] [RFC PATCH v3 4/4] virtio-rtc: Add normative statements for " Peter Hilber
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=20231218064253.9734-1-peter.hilber@opensynergy.com \
--to=peter.hilber@opensynergy.com \
--cc=cohuck@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.oasis-open.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).