ax_spi_write(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ax_spi_write(9) — like, the Kernel API Manual edition, bestie 🎀

Okay so real talk, this page is about ax_spi_write, and honestly? It's giving "one job, does it well." ✨ It's a register write — 32 bit per word, no cap.

🌸 NAME 🌸

ax_spi_write — Register write - 32 bit per word 💖

Like, that's it. That's the whole vibe. You write a 32-bit word into a register and you go about your day. Iconic behavior, honestly. 👑

🦋 SYNOPSIS 🦋

void ax_spi_write (struct ax_spi *xspi , u32 offset , u32 val );

Not me swooning over a function signature that returns void 😭 — it just does the thing and gives you nothing back. Main character energy fr fr. 💅

✨ ARGUMENTS ✨

  • xspi — Pointer to the ax_spi structure 🫶. Like, this is your lil' SPI buddy, the whole context you're working inside of. Point at it. Respect it.
  • offset — Register offset address 📍. This is the "where" of it all — which register you're sliding into. Choose wisely, bestie.
  • val — Value to write into that register 💌. A whole u32 of payload, hand-delivered to offset. Slay.
Ngl, the types here are doing a lot of the talking: xspi is a struct ax_spi *, and both offset and val are u32. Keep that in mind so you don't hand it something cursed. 🙈

🔥 SEE ALSO 🔥

Kernel file ./drivers/spi/spi-axiado.c — go read it, iykyk 💜 — plus the whole friend group:

Literally the entire squad, all listed, no one left behind 🫶💖

🧚 Sign-off 🧚

This lil' page lives under ./drivers/spi and it's dated October 2026 — put that in your calendar, bestie 📅✨. That's the whole thing! Go write your 32-bit words, stay hydrated, and remember: void means you get no tea back, and that's okay. 💀🌸💅

📦 where this page comes from