viortc_class_get_locked(9)

💅 viortc_class_get_locked(9)

okay so bestie, welcome to the Kernel API Manual ✨ you're literally reading viortc_class_get_locked(9) and honestly? she's a little baddie with one job. let's get into it 🎀

---

✨ NAME ✨

viortc_class_get_locked — grab the RTC class wrapper, but only if the ops are allowed 👀 no cap, that's the whole vibe.

---

🌸 SYNOPSIS 🌸

struct viortc_class * viortc_class_get_locked (struct device *dev );

that's it. that's the whole function signature. short king energy 👑

---

🦋 ARGUMENTS 🦋

• dev — the virtio device. yeah. that one. the device. give her the device 💖

---

🧚 DESCRIPTION 🧚

so like, this function gets the RTC class wrapper from the virtio device — but only if it's actually available and the ops are allowed ✅. both conditions, bestie, it's giving "you need to meet the requirements" energy. if either one's not happening, no wrapper for you 🙈

---

🔥 CONTEXT 🔥

⚠️ caller must hold rtc_lock. this is not a suggestion, this is the law 💀 lock it up before you call, fr fr.

---

⭐ RETURN ⭐

• the RTC class wrapper — when it's available and ops are allowed 🫶 slay
• ERR_PTR — otherwise 😭 that's the whole deal, no in-between

---

🌈 SEE ALSO 🌈

• kernel file ./drivers/virtio/virtio_rtc_class.c
• struct viortc_class(9)
• viortc_class_read_time(9)
• viortc_class_read_alarm(9)
• viortc_class_set_alarm(9)
• viortc_class_alarm_irq_enable(9)
• viortc_class_alarm(9)
• viortc_class_stop(9)
• viortc_class_register(9)
• viortc_class_init(9)

the whole friend group honestly 💜 go read them all, iykyk

---

and that's the page!! 🍓 this iconic lil entry lives in ./drivers/virtio and the version vibes are dated October 2026 — mwah, periodt 💅✨