thc_rxdma_read(9)
πΈ 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 π
- Kernel file
./drivers/hid/intel-thc-hid/intel-thc/intel-thc-dma.cβ go read the source, iykyk π thc_dma_set_max_packet_sizes(9)thc_dma_allocate(9)thc_dma_release(9)thc_dma_configure(9)thc_dma_unconfigure(9)thc_rxdma_reset(9)thc_swdma_read(9)thc_dma_write(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms