STRUCT SLIM_VAL_INF(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct slim_val_inf(9) πŸ’–

okay so bestie, welcome to the Kernel API Manual β€” this is the page for struct slim_val_inf, and yes it's giving "tiny struct, big responsibilities" ✨


🌸 NAME 🌸

struct slim_val_inf β€” the Slimbus value-or-information-element struct. that's literally it. it's the little guy that carries your values around πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

struct slim_val_inf {
    u16 start_offset;
    u8 num_bytes;
    u8 *rbuf;
    const u8                *wbuf;
    struct completion      *comp;
 };

look at her. five members. no notes. πŸ”₯


πŸ¦‹ Members πŸ¦‹

  • start_offset β€” where the party starts πŸŽ‰ this is the starting offset in the information/value element map. iykyk.
  • num_bytes β€” up to 16. and why 16, you ask?? because that's what makes the message fit the slicesize per the SLIMbus spec 🫢 so like, don't go over 16, fr fr.
  • rbuf β€” the buffer you read the values into. your reading-era main character buffer πŸ“–βœ¨
  • wbuf β€” the buffer you write from. note it's a const u8 * bestie, so hands off the contents πŸ’…
  • comp β€” a struct completion for asynchronous operations. important caveat: it's valid only if a TID is required for the transaction β€” like REQUEST operations. the rest of the transactions are synchronous anyway, so like... chill πŸ˜ŒπŸ’€

⭐ SEE ALSO ⭐

  • Kernel file ./include/linux/slimbus.h
  • struct slim_eaddr(9)
  • enum slim_device_status(9)
  • struct slim_device(9)
  • struct slim_driver(9)
  • struct slim_stream_config(9)
  • module_slim_driver(9)

go read those next, bestie, they're all linked in the same header πŸ‘‘πŸŒˆ


and that's the whole page!! this one lives in ./include/linux and the manual is dated October 2026 β€” mwah, bye, slay πŸ§šπŸ’– πŸŽ€

πŸ“¦ where this page comes from