viortc_alarms_supported(9)

💖 viortc_alarms_supported(9) 💖

okay so this page comes from the Kernel API Manual, and it's literally just checking whether a virtio device and its driver are both down with alarm support. yes bestie, we're doing a vibe check on alarms 💅✨

---

🌸 NAME 🌸

viortc_alarms_supported — whether device and driver support alarms. that's the whole assignment, no cap 🫶

✨ SYNOPSIS ✨

bool viortc_alarms_supported (struct virtio_device *vdev );

🎀 ARGUMENTS 🎀

• vdev — the virtio device. that's the one we're checking, periodt 💖

💅 DESCRIPTION 💅

quick heads-up, bestie: NB: Device and driver may not support alarms for the same clocks.

like... just because both sides are in the group chat doesn't mean they're matching on every clock, iykyk 🕰️💀

🦋 CONTEXT 🦋

Any context. literally any context — no special context requirements here 🌈

🔥 RETURN 🔥

True if both device and driver can support alarms. that's the condition, fr fr 👑

💖 SEE ALSO 💖

the Kernel file is ./drivers/virtio/virtio_rtc_driver.c, and the whole related-API squad is:

• struct viortc_vq(9)
• struct viortc_dev(9)
• struct viortc_msg(9)
• viortc_class_from_dev(9)
• viortc_feed_vq(9)
• viortc_msg_init(9)
• viortc_msg_release(9)
• viortc_do_cb(9)
• viortc_requestq_hdlr(9)
• viortc_cb_requestq(9)
• viortc_alarmq_hdlr(9)
• viortc_cb_alarmq(9)
• viortc_get_resp_errno(9)
• viortc_msg_xfer(9)
• VIORTC_DECLARE_MSG_HDL_ONSTACK(9)
• VIORTC_MSG(9)
• VIORTC_MSG_INIT(9)
• VIORTC_MSG_WRITE(9)
• VIORTC_MSG_READ(9)
• viortc_read(9)
• viortc_read_cross(9)
• viortc_cfg(9)
• viortc_clock_cap(9)
• viortc_cross_cap(9)
• viortc_read_alarm(9)
• viortc_set_alarm(9)
• viortc_set_alarm_enabled(9)
• viortc_init_rtc_class_clock(9)
• viortc_init_ptp_clock(9)
• viortc_init_clock(9)
• viortc_clocks_deinit(9)
• viortc_clocks_init(9)
• viortc_populate_vq(9)
• viortc_alloc_vq_bufs(9)
• viortc_init_vqs(9)
• viortc_probe(9)
• viortc_remove(9)

xoxo, this page's source/version is ./drivers/virtio, and the date on it is October 2026 — mwah 💋🎀