viortc_init_rtc_class_clock(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… viortc_init_rtc_class_clock(9)

okay so bestie, buckle up β€” this one's from the Kernel API Manual, section 9, and it's all about getting your RTC class device born and registered. it's giving "birth announcement but make it kernel" πŸŽ€


✨ NAME ✨

viortc_init_rtc_class_clock β€” literally init and register a RTC class device. that's the whole vibe. no cap. πŸ•°οΈ


🌸 SYNOPSIS 🌸

int viortc_init_rtc_class_clock (struct viortc_dev *viortc , u16
vio_clk_id , u8 clock_type , u8 flags );

like, it returns an int, and it takes four things. we love a simple signature. 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • viortc β€” the device data. it's the main character here, honestly. πŸ‘‘
  • vio_clk_id β€” the virtio_rtc clock id. it's a u16, iykyk. πŸ”₯
  • clock_type β€” the virtio_rtc clock type. a u8 this time. ⭐
  • flags β€” these are the struct virtio_rtc_resp_clock_cap.flags. yes, those flags. πŸ’…

πŸ’– DESCRIPTION πŸ’–

the clock must be a UTC-like clock. that's it. that's the requirement. don't come in here with your non-UTC-like nonsense, bestie, it's not the vibe. 😭


🌈 CONTEXT 🌈

Process context. periodt. 🧚


πŸ”₯ RETURN πŸ”₯

  • Positive β†’ if it got registered. slay, it worked. ✨
  • Zero β†’ if it's not supported by configuration. not a flop, just not the moment. πŸ™ˆ
  • Negative β†’ an error code otherwise. it's giving πŸ’€, check your stuff.

πŸ‘‘ SEE ALSO πŸ‘‘

okay this list is long, but every single one of these is iconic in its own right, so we're listing them all, fr fr:

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_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_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)


and that's the whole page, bestie πŸ“ k bye, this came from ./drivers/virtio, dated October 2026, and it's filed under viortc_init_rtc_class_clock(9) πŸ’œβœ¨

πŸ“¦ where this page comes from