STRUCT OPTEE_RTC(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– 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 the struct 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