thc_spi_inp...dress_config(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… thc_spi_input_output_address_config πŸ’…

okay so bestie, welcome to the kernel API manual ✨ (yes, the real one, not a vibe-only summary). this page is literally all about thc_spi_input_output_address_config β€” the glow-up that configures your SPI input and output addresses πŸŽ€


🌸 NAME 🌸

thc_spi_input_output_address_config β€” configure SPI input and output addresses. that's it, that's the whole errand πŸ’–


✨ SYNOPSIS ✨

void thc_spi_input_output_address_config (struct thc_device *dev , u32
input_hdr_addr , u32 input_bdy_addr , u32 output_addr );

like, it returns void, so don't be out here expecting a little receipt back, okay? 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the pointer of THC private device context πŸ’… your main character struct, the one holding all the private tea.
  • input_hdr_addr β€” input report header address. the header part, bestie, not the body, we're being specific ✨
  • input_bdy_addr β€” input report body address. yes, the body, the glow-up portion of the input report πŸ”₯
  • output_addr β€” output report address. where the output report lives, iconic, no notes πŸ’œ

πŸ‘‘ SEE ALSO πŸ‘‘

kernel file ./drivers/hid/intel-thc-hid/intel-thc/intel-thc-dev.c β€” go read it, iykyk πŸ“–

and the whole friend group, alphabetically-ish assembled for your convenience πŸ’–

bestie note: that's 26 functions in SEE ALSO and not me skipping a single one, we do not do that here πŸ’€πŸ’…

and that's the page!! πŸŽ€ from ./drivers/hid/intel-thc-hid/in..., dated October 2026, page thc_spi_inp...dress_config(9) β€” mwah, slay, go configure those addresses πŸŒˆβ­πŸ¦‹

πŸ“¦ where this page comes from