ti_sci_get_one_xfer(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ti_sci_get_one_xfer(9) πŸ’–

okay bestie, welcome to the Kernel API Manual β€” this page is literally all about ti_sci_get_one_xfer, and yes, it's giving β€œallocate one message” main character energy. πŸŽ€βœ¨

🌸 NAME 🌸

ti_sci_get_one_xfer β€” Allocate one message

✨ SYNOPSIS ✨

struct ti_sci_xfer * ti_sci_get_one_xfer (struct ti_sci_info *info , u16
       msg_type , u32 msg_flags , size_t tx_message_size , size_t
       rx_message_size );

πŸ’… ARGUMENTS πŸ’…

  • info β€” Pointer to SCI entity information.
  • msg_type β€” Message type.
  • msg_flags β€” Flag to set for the message.
  • tx_message_size β€” transmit message size.
  • rx_message_size β€” receive message size.

πŸ¦‹ DESCRIPTION πŸ¦‹

This is the helper function that the various command functions exposed to clients of this driver use when they need to allocate a message traffic event. She's a team player like that. πŸ’–

Depending on pending requests already in the system for the SCI entity, this function can sleep 😴 β€” yes, literally. It also holds a spinlock to maintain integrity of internal data structures.

bestie, it can sleep and it holds a spinlock β€” both facts are right there in the description, so respect the vibe. 🫢

πŸ”₯ RETURN πŸ”₯

It returns 0 if all went fine πŸŽ‰, otherwise you get the corresponding error 😭.

πŸ”— SEE ALSO πŸ”—

Kernel file: ./drivers/firmware/ti_sci.c β€” and here's the full squad, every single one, no skips:


mwah πŸ’‹ that's the whole page, bestie! source/version is ./drivers/firmware, it's dated October 2026, and the page is ti_sci_get_one_xfer(9) β€” bye! 🫢✨

πŸ“¦ where this page comes from