STRUCT OPTEE_RTC(9)
π struct optee_rtc β OP-TEE RTC private data π
okay so bestie, welcome to the Kernel API Manual, and buckle up because we're about to vibe check a struct π¦
β¨ NAME β¨
struct optee_rtc β the private data for the OP-TEE RTC, no cap π
πΈ SYNOPSIS πΈ
struct optee_rtc {
struct device *dev;
struct tee_context *ctx;
u32 session_id;
u32 session2_id;
struct tee_shm *shm;
u64 features;
struct task_struct *alarm_task;
struct rtc_device *rtc;
};
like, that's the whole thing. she's compact, she's iconic, she's giving main character energy π
π Members π
devβ the OP-TEE based RTC device. literally the device itself, the whole reason we're here π«Άctxβ the OP-TEE context handler. the handler of the OP-TEE context, fr fr β¨session_idβ the RTC TA session identifier. this is the TA session ID for the RTC πsession2_idβ the RTC wait alarm session identifier. a second session ID, specifically for the RTC wait alarm π¦shmβ the memory pool shared with the RTC device. shared memory, shared vibes πfeaturesβ bitfield of RTC features. it's a bitfield. of features. we love a bitfield πalarm_taskβ the RTC wait alamr task. (that's "alarm," she just typed it like that and honestly? iconic π) the task for the RTC wait alarm πrtcβ the RTC device. yes, again, but this one's thestruct rtc_device *. the icon herself β
ngl, some of these descriptions are doing the absolute bare minimum and honestly, same. but every single member is listed, so nothing got left on read π
π₯ SEE ALSO π₯
- Kernel file
./drivers/rtc/rtc-optee.cβ go read her, she's the source of truth π§
aaaand that's the page!! no crumbs left behind, every field accounted for π
so anyway, this little beauty lives in ./drivers/rtc, she's dated October 2026, and she answers to struct optee_rtc(9) β periodt. πβ¨π¦π
π¦ 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