sdio_writeb(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… sdio_writeb(9) β€” like, the Kernel API Manual, but make it make sense

okay so bestie, welcome to sdio_writeb(9) from the Kernel API Manual β€” yes it's a real kernel function and yes it's lowkey iconic. it writes one single byte to an SDIO function. one. byte. minimalism ate fr fr πŸ’–


✨ SYNOPSIS ✨

void sdio_writeb (struct sdio_func *func , u8 b , unsigned int addr ,
       int *err_ret );

look at her go. five-ish things in, nothing out, very mysterious main character energy πŸŽ€


🌸 ARGUMENTS 🌸

  • func β€” the SDIO function you're accessing, i.e. the thing you're writing into. your little target 🫢
  • b β€” the byte you want to write. it's a u8, so one byte, no more, no notes πŸ’…
  • addr β€” the address you're writing to. it's an unsigned int, so pick your spot wisely ✨
  • err_ret β€” optional status value from the transfer. optional!! she's not mandatory, but she will tell you how it went πŸ‘€

πŸ’œ DESCRIPTION πŸ’œ

So basically: this writes a single byte to the address space of a given SDIO function. that's it, that's the whole vibe. one byte, one address, no drama.

and err_ret will contain the status of the actual transfer β€” so if you passed in a pointer, you get the tea on whether it worked or not. ngl it's giving "small function, big responsibility" πŸ”₯

reminder: err_ret is described as optional, so don't act surprised when it's a pointer you can skip. the status of the actual transfer is what lands there when you do pass it πŸ¦‹

πŸ‘‘ SEE ALSO πŸ‘‘

kernel file ./drivers/mmc/core/sdio_io.c β€” and literally the whole SDIO friend group, all here, all slaying:

like, the whole group chat showed up. we love a supportive community 🌈


okay that's the page!! this one came from ./drivers/mmc/core, dated October 2026, and it's filed under sdio_writeb(9) in the Kernel API Manual. go write your one byte bestie, you got this πŸ’–βœ¨πŸ“

πŸ“¦ where this page comes from