viortc_clocks_init(9)

✨ viortc_clocks_init — the kernel API manual, bestie edition ✨

okay so real talk, this is viortc_clocks_init from the Kernel API Manual and it's literally the glow-up moment for virtio_rtc clocks 💅

---

💖 NAME 💖

viortc_clocks_init — init local representations of virtio_rtc clocks

like, it's giving "set up the local version of your virtio_rtc clocks" energy, no cap 🕰️✨

---

🎀 SYNOPSIS 🎀

int viortc_clocks_init (struct viortc_dev *viortc );

one function, one argument, one int coming back at you 🫶

---

🌸 ARGUMENTS 🌸

• viortc — device data. that's the whole vibe. it's the struct viortc_dev * you're handing over 💜

---

🦋 CONTEXT 🦋

Process context. so like, process context specifically — don't come at it from just anywhere, iykyk ⭐

---

🔥 RETURN 🔥

Zero on success, negative error code otherwise. zero = slayed, negative = it's giving unfortunate 😭💀

---

👑 SEE ALSO 👑

Kernel file ./drivers/virtio/virtio_rtc_driver.c

and the whole friend group, fr fr:

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_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_populate_vq(9), viortc_alloc_vq_bufs(9), viortc_init_vqs(9), viortc_probe(9), viortc_remove(9)

like that's a whole squad, and they ALL ate 🌈🍓

---

anyway bestie, this page lives under ./drivers/virtio, dated October 2026, and it's filed as viortc_clocks_init(9) — go off, read the source, main character energy only 💅✨🎀🦋