sdio_writesb(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… sdio_writesb β€” bestie's guide to yeeting bytes into a FIFO

okay so this is a page from the Kernel API Manual (section 9, the kernel-space girlies πŸ’–), and it's all about sdio_writesb, which is lowkey iconic for one specific job: writing into the FIFO of an SDIO function. no cap, that's the whole vibe.


✨ NAME ✨

sdio_writesb β€” write to a FIFO of a SDIO function πŸŽ€


🌸 SYNOPSIS 🌸

int sdio_writesb (struct sdio_func *func , unsigned int addr , void *src
, int count );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • func β€” the SDIO function you're accessing πŸ’« like, whose FIFO are we talking to
  • addr β€” address of the (single byte) FIFO, yes literally one byte, that's the whole address, don't come for me
  • src β€” the buffer holding the data you're about to write πŸ‘‘ this is where your bytes live before they get sent
  • count β€” number of bytes to write, so be honest about how many you're sending πŸ“

🌈 DESCRIPTION 🌈

So the way this works: sdio_writesb writes to the specified FIFO of a given SDIO function. That's it, that's the whole personality. ✨

The return value tells you whether the transfer succeeded or not β€” so like, check it, bestie, don't just ignore it and assume everything's fine πŸ’€


πŸ’œ SEE ALSO πŸ’œ

Kernel file ./drivers/mmc/core/sdio_io.c (the source of truth, go read it, iykyk 🧚), plus the whole friend group:


πŸ’… fr fr that's the whole page. go write to your FIFO, main character.

big kiss, this came from ./drivers/mmc/core and it's dated October 2026 β€” slay, bye πŸ«ΆπŸ’–

πŸ“¦ where this page comes from