sdio_f0_writeb(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ sdio_f0_writeb(9) ✨

okay bestie, bestie, BESTIE β€” gather round, because we're in the Kernel API Manual today and this page is a lil tiny one but it's literally so important, ngl πŸ’…


πŸŽ€ NAME πŸŽ€

sdio_f0_writeb β€” write a single byte to SDIO function 0


πŸ¦‹ SYNOPSIS πŸ¦‹

void sdio_f0_writeb (struct sdio_func *func , unsigned char b , unsigned
int addr , int *err_ret );

like, that's the whole squad right there 🫢


🌸 ARGUMENTS 🌸

  • func β€” an SDIO function of the card. yes, the actual function struct, she's the main character here πŸ‘‘
  • b β€” the byte to write. just one. that's her whole job πŸ“
  • addr β€” the address you're writing to πŸ“
  • err_ret β€” optional status value from the transfer. optional, but like... your bestie over here? she wants to know how it went 😭

πŸ’– DESCRIPTION πŸ’–

So the vibe is: this writes a single byte into the address space of SDIO function 0. one byte, no more, no cap. and err_ret will contain the status of the actual transfer β€” so if you passed a pointer in, you get the tea on whether it worked. ⭐

IMPORTANT VIBE CHECK 🚨 only writes to the vendor specific CCCR registers (0xF0 - 0xFF) are permitted. if you try to write anywhere outside that range, err_ret gets set to -EINVAL and the kernel is like "girl. no." πŸ’€

so yeah β€” stay in your lane (0xF0 to 0xFF), and everything's slay. wander out of it and you get -EINVAL. that's the whole boundary situation, periodt. 🌈


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/mmc/core/sdio_io.c, plus the whole friend group:


and that's the page!! 🧚 this lil icon of a manpage lives under ./drivers/mmc/core, it's from October 2026, and you can find it filed as sdio_f0_writeb(9) β€” go off, write that one byte, stay inside 0xF0 - 0xFF, and stan a kernel dev today πŸ’œβœ¨πŸŽ€

πŸ“¦ where this page comes from