spi_nor_wri...cr_and_check(9)

📦 version 7.3.1, in nixpkgs unstable

💅 spi_nor_wri...cr_and_check(9) — Kernel API Manual, bestie edition ✨

okay so you opened the kernel API manual, and the vibe is immaculate. welcome to spi_nor_write_sr_cr_and_check, a function that writes the Status Register 1 and then ✨double-checks✨ that the byte it wrote actually matches the value it received. no cap, it does the exact same thing for the Control Register too, if there is one. it's giving "trust but verify" and honestly? iconic. 🎀

🌸 SYNOPSIS 🌸

int spi_nor_write_sr_cr_and_check (struct spi_nor *nor , const u8 *regs
);

like literally that's the whole signature. look at her go 💖

🦋 ARGUMENTS 🦋

  • nor — pointer to a struct spi_nor, i.e. your main character struct. she's the one holding everything together, periodt. 👑
  • regs — byte array to be written to the registers. it's the actual payload, the ~moment~, the thing that gets shipped off to the registers. 📦

⭐ RETURN ⭐

0 on success, -errno otherwise. that's it, that's the whole mood. 0 = slay, -errno = not slay (and the errno will tell you why, iykyk). 😭

🌈 SEE ALSO 🌈

the whole friend group, fr fr. every single one of these linked (9) manpages, in the exact order the kernel gave them to us:

💀 real talk: there are a LOT of them. that's 62 links, bestie, and not one of them got skipped. go read them all, or at least the ones that vibe with your current bug. 🫶

also worth knowing: this page lives in the Kernel file ./drivers/mtd/spi-nor/core.c. 📁

and that's the whole page! mwah 💋 this little beauty is from ./drivers/mtd/spi-nor, dated October 2026, and yes the header still says spi_nor_wri...cr_and_check(9) because the kernel was too real to spell it all out. bye bestie, go write some registers 🧚💜

📦 where this page comes from