spi_offload_trigger_enable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ spi_offload_trigger_enable(9) πŸ¦‹

okay so this one is straight out of the Kernel API Manual, and it’s giving β€œlet the offload trigger cook” energy πŸ’…βœ¨


✨ NAME ✨

spi_offload_trigger_enable β€” enables the trigger for offload, periodt πŸ’–


🌸 SYNOPSIS 🌸

int spi_offload_trigger_enable (struct spi_offload *offload , struct
       spi_offload_trigger *trigger , struct spi_offload_trigger_config *config
       );

πŸŽ€ ARGUMENTS πŸŽ€

  • offload β€” the offload instance, bestie 🫢
  • trigger β€” the offload trigger instance ✨
  • config β€” the trigger config that needs to be validated πŸ‘‘

πŸ’œ DESCRIPTION πŸ’œ

okay so before this can do its thing, there has to be a prepared offload instance with the specified ID, meaning spi_optimize_message was called with the same offload assigned to the message. no cap, that’s the setup requirement πŸ”₯

this also reserves the bus for exclusive use by the offload instance until the trigger is disabled. during that time, any other attempts to send a transfer or lock the bus will fail with -EBUSY β€” like, the bus is literally booked and busy πŸ’€

calls must be balanced with spi_offload_trigger_disable, bestie. don’t leave it hanging πŸ™ˆ

🧚 CONTEXT 🧚

can sleep πŸ˜΄πŸ’€ β€” yes, this one is allowed to snooze.


🌈 RETURN 🌈

0 on success, otherwise a negative error code πŸ’–


⭐ SEE ALSO ⭐


mwah πŸ’– this little page came from ./drivers/spi, dated October 2026, and it’s all about spi_offload_trigger_enable(9). bye bestie πŸ«ΆπŸ’…

πŸ“¦ where this page comes from