viortc_cross_cap(9)

💅 viortc_cross_cap(9) 💅

okay so this page is from the Kernel API Manual, and it's literally about viortc_cross_cap — the VIRTIO_RTC_REQ_CROSS_CAP wrapper. Bestie, it's a tiny kernel helper and we're gonna get into every single detail, no skipping. 🫶

---

🌸 NAME 🌸

viortc_cross_cap — a VIRTIO_RTC_REQ_CROSS_CAP wrapper.

✨ SYNOPSIS ✨

the signature, exactly as it appears, because we do not mess with code around here:

int viortc_cross_cap (struct viortc_dev *viortc , u16 vio_clk_id , u8
hw_counter , bool *supported );

🎀 ARGUMENTS 🎀

meet the cast, bestie:

• viortc — device data.
• vio_clk_id — virtio_rtc clock id.
• hw_counter — virtio_rtc HW counter type.
• supported — says whether xtstamping is supported for the vio_clk_id/hw_counter pair. (yes, that exact pair 💅)

🦋 CONTEXT 🦋

Process context. That's it, that's the context. 🦋

🔥 RETURN 🔥

Zero on success, negative error code otherwise. periodt.

💖 SEE ALSO 💖

the kernel file is ./drivers/virtio/virtio_rtc_driver.c, and the whole friend group shows up here:

• struct viortc_vq(9)
• struct viortc_dev(9)
• struct viortc_msg(9)
• viortc_class_from_dev(9)
• viortc_alarms_supported(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_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)

okay bye bestie 🫶 this page is from ./drivers/virtio, dated October 2026, and the title is viortc_cross_cap(9) — slay and stay hydrated ✨