viortc_class_init(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– viortc_class_init(9) πŸ’–

Okay bestie, welcome to the Kernel API Manual page for viortc_class_init(9) β€” yes, the manual name is right there, we're being efficient. This one is all about setting up the RTC class wrapper and device. Let's get into it, no cap. ✨


✨ NAME ✨

viortc_class_init β€” init RTC class wrapper and device. That's the whole assignment, and it ate. πŸ’…

🌸 SYNOPSIS 🌸

struct viortc_class * viortc_class_init (struct viortc_dev *viortc , u16
vio_clk_id , bool have_alarm , struct device *parent_dev );

πŸŽ€ ARGUMENTS πŸŽ€

  • viortc β€” device data. The device's whole lore, basically. 🫢
  • vio_clk_id β€” virtio_rtc clock id. Yep, the virtio_rtc clock id, exactly as advertised. πŸ•°οΈ
  • have_alarm β€” have alarm feature. A bool saying whether the alarm feature is, like, present. 🚨
  • parent_dev β€” virtio device. The parent virtio device, main character energy. πŸ‘‘

πŸ’… CONTEXT πŸ’…

Process context. That's it. Run it in process context, bestie. 🧚

πŸ¦‹ RETURN πŸ¦‹

RTC class wrapper on success, ERR_PTR otherwise. So: slay on success, ERR_PTR when it's not giving. πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/virtio/virtio_rtc_class.c, plus these absolute icons:


And that's the page! Signing off with source/version ./drivers/virtio, dated October 2026, for viortc_class_init(9). Stay iconic, kernel bestie πŸ’–πŸŒˆβœ¨

πŸ“¦ where this page comes from