STRUCT EC_RTC_READ_RESPONSE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ struct ec_rtc_read_response πŸ’–

okay bestie so this is from the Kernel API Manual and it's literally just the layout of the RTC (that's real-time clock, iykyk) that the EC hands back to you. it's giving very structured. very demure. let's get into it πŸŽ€


🌸 NAME 🌸

struct ec_rtc_read_response β€” the format of the RTC that gets returned by the EC. no cap, that's the whole vibe. ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

struct ec_rtc_read_response {
    u8 reserved;
    u8 second;
    u8 minute;
    u8 hour;
    u8 day;
    u8 month;
    u8 year;
    u8 century;
 };

look at her. eight u8 fields, all lined up, main character energy fr fr. πŸ’…


πŸ‘‘ Members πŸ‘‘

  • reserved β€” an unused byte 🫢 she's just there for the vibes, do not perceive her
  • second β€” the seconds, 0..59 ⭐
  • minute β€” the minutes, 0..59 πŸ•
  • hour β€” the hours, 0..23 πŸ”₯
  • day β€” the day, 1..31 🌈
  • month β€” the month, 1..12 🌸
  • year β€” the year, and it's the full year % 100 bestie, so like the last two digits basically πŸ’œ
  • century β€” the century, and that one's the full year / 100 🧚

πŸ’€ Description πŸ’€

okay so important thing: all values are presented in binary (not BCD). literal slay. no BCD nonsense here, we're raw binary and we're proud of it. ✨


πŸ” SEE ALSO πŸ”

  • the kernel file ./drivers/rtc/rtc-wilco-ec.c β€” go read her, she's iconic πŸ’–
  • struct ec_rtc_write_request(9) β€” the write-side twin, equally iconic, equally ec_rtc πŸ¦‹

ngl if you forget the binary-not-BCD thing you WILL be confused and it WILL be a whole situation 😭 so like. remember it. periodt.

kisses and good luck bestie, this page lives in ./drivers/rtc and she's dated October 2026 β€” struct ec_rtc_read_response(9) forever and always πŸŽ€πŸ’…βœ¨

πŸ“¦ where this page comes from