eeprom_93cx6_write(9)
π 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 addressaddr. 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 π
- Kernel file
./drivers/misc/eeprom/eeprom_93cx6.cβ the source, the origin story π eeprom_93cx6_read(9)eeprom_93cx6_multiread(9)eeprom_93cx6_readb(9)eeprom_93cx6_multireadb(9)eeprom_93cx6_wren(9)
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
- 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