eeprom_93cx6_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… eeprom_93cx6_write(9) πŸ’…

okay bestie, welcome to the Kernel API Manual β€” today's main character is eeprom_93cx6_write, and honestly? she's doing exactly what her name says. no plot twists, no cap.


🌸 NAME 🌸

eeprom_93cx6_write β€” write data to the EEPROM βœοΈπŸ’Ύ


✨ SYNOPSIS ✨

void eeprom_93cx6_write (struct eeprom_93cx6 *eeprom , u8 addr , u16
data );

that's it, that's the whole vibe check. three things go in, nothing comes back out (it's void, she doesn't do returns πŸ’β€β™€οΈ).


πŸŽ€ ARGUMENTS πŸŽ€

  • eeprom β€” pointer to the eeprom structure 🫢 like, the whole little EEPROM world you're about to write into.
  • addr β€” the address to write data to. where you're dropping the data off, basically πŸ“
  • data β€” the data you're writing to address addr. the actual payload, the moment, the reason we're all here πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

so what she does is: write the data to the specified addr in the EEPROM, and then wait for the device to finish writing. that waiting part is not optional, bestie β€” the device needs a sec to actually commit, and we're being polite about it 😌✨

now, the note in the source, and this is lowkey important: since we do not expect a large number of write operations, we delay in between parts of the operation β€” on purpose! β€” to avoid using excessive amounts of CPU time busy waiting. like, why spin the CPU at 100% when you could just chill for a moment instead? it's giving ✨healthy boundaries✨. ngil (not gonna lie, this is a cpu-friendly choice) πŸ”₯

fr fr though, this is a deliberate design choice, not laziness β€” the delay between parts of the operation exists to keep from burning CPU cycles in a busy wait. 🧚

🌈 SEE ALSO 🌈

like the whole friend group, all linked up πŸ’œπŸ’«


okay that's the page!! and for the cute sign-off: this one lives in ./drivers/misc/eeprom, dated October 2026 β€” so yeah, she's got a timestamp, a home directory, and a whole lot of ~waiting for the hardware~ energy. slay, write that EEPROM, and remember to be patient with your devices πŸŽ€πŸ«ΆπŸ’…

πŸ“¦ where this page comes from