ds1685_rtc_b..._data_access(9)

📦 version 7.3.1, in nixpkgs unstable

💖 ds1685_rtc_begin_data_access — NAME 💖

Okay so bestie, this is ds1685_rtc_begin_data_access — it literally preps the rtc so you can actually get at its data. Like, it sets the whole thing up so data access can happen. Periodt. ✨

(Also hi, you're reading the ds1685_rtc_b..._data_access(9) page from the Kernel API Manual — the truncated-name thing is so real, iykyk 🫶)

🌸 SYNOPSIS 🌸

void ds1685_rtc_begin_data_access (struct ds1685_priv *rtc );

No return value, she just does the thing. 💅

🎀 ARGUMENTS 🎀

  • rtc — a pointer to the ds1685 rtc structure. That's your girl. 🦋

✨ DESCRIPTION ✨

So to get/set time and alarm values out of the rtc registers, you can't just waltz in there — this function takes several steps to prepare the rtc for that access. It's giving getting-ready-with-me, but for hardware. Obsessed. 🧚

Here's the whole routine, in order:

  • Sets the SET bit in Control Register B. ✅
  • Reads Ext Control Register 4A and checks the INCR bit. 👀
  • If INCR is active, a short delay is added before Ext Control Register 4A is read again, in a loop, until INCR is inactive. She will wait for it, no cap. ⏳
  • Switches the rtc to bank 1. This is the iconic part — it's what lets you access all the relevant data for normal rtc operation, because bank 0 contains only the nvram. Bank 0 is lowkey just the nvram shelf. 🗄️✨

🌈 SEE ALSO 🌈

The whole squad, all present and accounted for 💜:

Kernel file ./drivers/rtc/rtc-ds1685.c

Heads up bestie: if you opened this page expecting ds1685_rtc_end_data_access, that's a whole other function — she's in the SEE ALSO list above, go say hi 🫶

Okay that's the page!! Mwah 💋 This one lives in ./drivers/rtc, and the version stamp says October 2026 — so like, future vibes only. Go forth and access your data responsibly, icon. 👑💖

📦 where this page comes from