viortc_init_ptp_clock(9)

💖 NAME 💖

viortc_init_ptp_clock — init and register PTP clock. that's the whole assignment, bestie. this is the Kernel API Manual page for viortc_init_ptp_clock(9), and it's giving “kernel API but make it cute” ✨

🎀 SYNOPSIS 🎀

int viortc_init_ptp_clock (struct viortc_dev *viortc , u16 vio_clk_id ,
u8 clock_type , u8 leap_second_smearing );

🌸 ARGUMENTS 🌸

• viortc — device data. yes, the device data, no cap.
• vio_clk_id — virtio_rtc clock id.
• clock_type — virtio_rtc clock type.
• leap_second_smearing — virtio_rtc leap second smearing.

🦋 CONTEXT 🦋

Process context. that's the vibe, periodt. 💅

🔥 RETURN 🔥

• Positive — positive if registered. slay, it's in.
• Zero — zero if not supported by configuration. config said no, respectfully.
• Negative — negative error code otherwise. 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/virtio/virtio_rtc_driver.c plus the whole friend group: 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_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).

alright bestie, that's the whole page — source/version ./drivers/virtio, dated October 2026, for viortc_init_ptp_clock(9). bye and stay iconic 💜🫶