STRUCT PL031_VENDOR_DATA(9)
β¨ struct pl031_vendor_data(9) β¨
okay so bestie, welcome to the pl031_vendor_data glow-up π
this is a page from the Kernel API Manual, and it's literally all about the per-vendor variations β like, every silicon version has its own little personality and this struct is where the diffs live π«Ά
πΈ NAME πΈ
struct pl031_vendor_data β per-vendor variations π
π¦ SYNOPSIS π¦
struct pl031_vendor_data {
struct rtc_class_ops ops;
bool clockwatch;
bool st_weekday;
unsigned long irqflags;
time64_t range_min;
timeu64_t range_max;
};
no cap, that's the whole shape of it π
π Members π
opsβ the vendor-specific operations that get used on this particular silicon version. like, this is the main character of the struct fr fr β¨clockwatchβ aboolthat's set if this is an ST Microelectronics silicon version with a clockwatch function π°οΈst_weekdayβ aboolfor when this is an ST Microelectronics silicon version that need the weekday fix. yes bestie, the weekday fix is real and this flag is how you know πirqflagsβ the special IRQ flags, per variant. each one gets its own vibe check π₯range_minβ the minimum date/time supported by the RTC. the earliest era this thing will acknowledge β³range_maxβ the maximum date/time supported by the RTC. how far into the future we're allowed to go π
π SEE ALSO π
Kernel file ./drivers/rtc/rtc-pl031.c β go read it, iykyk π
lowkey a reminder: these are just the fields as documented here, so don't go inventing behaviour that isn't written down, bestie π
that's the whole page, periodt π
this one shipped out of ./drivers/rtc and it's dated October 2026 β mwah, drink some water and go read your kernel source ππ§π
π¦ 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