viortc_cfg(9)

🎀 NAME 🎀

This is viortc_cfg(9) from the Kernel API Manual, bestie — the VIRTIO_RTC_REQ_CFG wrapper. That's the whole name section, iconic and concise. 💅

---

✨ SYNOPSIS ✨

The signature is literally this, character for character:

int viortc_cfg (struct viortc_dev *viortc , u16 *num_clocks );

---

🫶 ARGUMENTS 🫶

• viortc — device data. Like, the device's data vibe, fr fr.
• num_clocks — the # of virtio_rtc clocks. That's the clock count, no cap. 🕰️

---

🧚 CONTEXT 🧚

It's Process context. That's the context, bestie — process context energy only. ✨

---

🌈 RETURN 🌈

Zero on success, and a negative error code otherwise. So if it returns 0, it ate; if it's negative, it's giving error. 😭

---

👑 SEE ALSO 👑

Okay so the SEE ALSO is a whole friend group — gather round, every single one is here:

• Kernel file ./drivers/virtio/virtio_rtc_driver.c
• 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_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)

mwah 💋 — this page's source is ./drivers/virtio, its date is October 2026, and the manual is viortc_cfg(9). Periodt. 🫶