STRUCT TI_K3_RTC(9)
π NAME π
okay so we're in the Kernel API Manual, and this page is literally all about struct ti_k3_rtc(9) β which is the private data for ti-k3-rtc, no cap. it's giving "backstage pass to the RTC driver" energy, and honestly? iconic. π
β¨ SYNOPSIS β¨
struct ti_k3_rtc {
unsigned int irq;
u32 sync_timeout_us;
unsigned long rate_32k;
struct rtc_device *rtc_dev;
struct regmap *regmap;
struct regmap_field *r_fields[K3_RTC_MAX_FIELDS];
};
like yes bestie, that's the whole struct layout, and every field is about to get its moment π
πΈ Members πΈ
irqβ the IRQ. that's it, that's the field. she's short and mysterious πsync_timeout_usβ the data sync timeout period in uSec. so, like, how long we're willing to wait before we're like "bestieβ¦ hello?" β³rate_32kβ the 32k clock rate in Hz. yes,32k, yes, Hz, we love a unit that ate π°οΈrtc_devβ the rtc device. main character pointer energy fr fr πregmapβ the rtc mmio regmap. the map to the mmio, not a vibe map, but honestly could be both πΊοΈr_fieldsβ the rtc register fields. plural, array-coded,K3_RTC_MAX_FIELDS-capped, slay π
lowkey just here to say: every member above is in the original and none of them got left on read π
π¦ SEE ALSO π¦
- Kernel file
./drivers/rtc/rtc-ti-k3.c k3rtc_fence(9)
like go read those too, iykyk π«Ά
mwah π β this cutie came from the source path ./drivers/rtc, version/date October 2026, and the page title is struct ti_k3_rtc(9). bye bestie, go forth and RTC responsibly π§π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms