slim_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ slim_write(9) β€” Kernel API Manual πŸ¦‹

okay bestie, this is the manual page for slim_write, and it’s giving β€œsmall function, very important little task.” no cap. ✨

πŸ’– NAME πŸ’–

slim_write β€” Write SLIMbus value element.

✨ SYNOPSIS ✨

int slim_write (struct slim_device *sdev , u32 addr , size_t count , u8
       *val );

πŸŽ€ ARGUMENTS πŸŽ€

  • sdev β€” client handle. Yes, that’s the one, bestie. πŸ’…
  • addr β€” address in the value element to write. Like the exact spot you’re pulling up to. πŸ“
  • count β€” number of bytes to write. Maximum bytes allowed are 16. 16 is the ceiling, periodt. 🚦
  • val β€” value to write to value element. The actual content, the main character of this operation. 🌟

🌈 RETURN 🌈

  • -EINVAL β€” for Invalid parameters. Bestie, the inputs were not it. πŸ’€
  • -ETIMEDOUT β€” If transmission of this message timed out (e.g. due to bus lines not being clocked or driven by controller). So yeah, the message tried to send but the bus situation was lowkey not cooperating. 😭

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/slimbus/messaging.c β€” and the whole friend group is: slim_msg_response(9), slim_alloc_txn_tid(9), slim_free_txn_tid(9), slim_do_transfer(9), slim_xfer_msg(9), slim_read(9), slim_readb(9), slim_writeb(9). obsessed with this friend group, iykyk. 🫢


made with πŸ’– from source/version ./drivers/slimbus, dated October 2026 β€” slim_write(9) signing off, periodt! πŸŽ€

πŸ“¦ where this page comes from