thc_rxdma_read(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 thc_rxdma_read(9) 🌸

okay bestie, welcome to the Kernel API Manual, section 9 πŸ’… this one's a read function and it's kind of a big deal, so let's get into it 🫢


✨ NAME ✨

thc_rxdma_read β€” literally just Read data from RXDMA buffer πŸ“–βœ¨ that's the whole vibe.


πŸ¦‹ SYNOPSIS πŸ¦‹

int thc_rxdma_read (struct thc_device *dev , enum thc_dma_channel
dma_channel , void *read_buff , size_t *read_len , int *read_finished );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the pointer of THC private device context. yep, your main character struct πŸ’œ
  • dma_channel β€” the RXDMA engine of read data source. it's giving "where the tea comes from" β˜•
  • read_buff β€” the pointer of the read data buffer. the little container your data lands in πŸ“
  • read_len β€” the pointer of the read data length. how much we're reading, noted and slayed πŸ“
  • read_finished β€” the pointer of the flag indicating if all pending data has been read out. that's the "are we done here or what" flag πŸ‘‘ no cap, once it says everything's drained, you're done.

πŸ”₯ RETURN πŸ”₯

0 on success, other error codes on failed. simple as that, periodt πŸ’€

fr fr bestie, check your return value. 0 is the slay outcome, anything else means something went sideways and you should deal with it πŸ™ˆ

🌈 SEE ALSO 🌈

the whole friend group, honestly πŸ’–


and that's the page! πŸŽ€ this lil manual came to you from ./drivers/hid/intel-thc-hid/in… and it's dated October 2026, filed under thc_rxdma_read(9) β€” mwah, go read some DMA buffers bestie πŸ’…βœ¨

πŸ“¦ where this page comes from