rtc_read_offset(9)

✨ NAME ✨

okay bestie, welcome to rtc_read_offset(9) from the Kernel API Manual 💅 this page is literally about one thing: reading the amount of rtc offset in parts per billion. That's the name, that's the assignment, periodt.

rtc_read_offset — Read the amount of rtc offset in parts per billion 🌸

🛠️ SYNOPSIS 🛠️

int rtc_read_offset (struct rtc_device *rtc , long *offset );

🎀 ARGUMENTS 🎀

• rtc — the rtc device to be used 🫶
• offset — the offset in parts per billion ✨

💖 DESCRIPTION 💖

The original literally says “see below for details.” and honestly? iconic. So here is the below, bestie 😭

This is the kernel interface to read rtc clock offset. It returns 0 on success, or a negative number on error. If read_offset is not implemented for the rtc, return -EINVAL 🚨

no cap, that's the whole behavior check: success gives 0, error gives a negative number, and a missing read_offset implementation gives -EINVAL 💀

🌈 SEE ALSO 🌈

Kernel file: ./drivers/rtc/interface.c 👑 and these absolute icons:

• rtc_read_next_alarm(9)
• rtc_handle_legacy_irq(9)
• rtc_aie_update_irq(9)
• rtc_uie_update_irq(9)
• rtc_pie_update_irq(9)
• rtc_update_irq(9)
• rtc_irq_set_state(9)
• rtc_irq_set_freq(9)
• rtc_timer_enqueue(9)
• rtc_timer_remove(9)
• rtc_timer_do_work(9)
• rtc_set_offset(9)

that's the whole page, mwah 💋 this cutie was brought to you by ./drivers/rtc, October 2026, and it's the rtc_read_offset(9) page from the Kernel API Manual 🫶💖✨