STRUCT DMA_CHAN_DEV(9)
π struct dma_chan_dev(9) π
okay bestie, welcome to the Kernel API Manual entry for struct dma_chan_dev β¨ its whole thing is literally to relate sysfs device node to backing channel device π
no cap.
πΈ NAME πΈ
struct dma_chan_dev β relate sysfs device node to backing channel device π«Ά
β SYNOPSIS β
struct dma_chan_dev {
struct dma_chan *chan;
struct device device;
int dev_id;
bool chan_dma_dev;
};
π«Ά Members π«Ά
chanβ driver channel device πdeviceβ sysfs device β¨dev_idβ parent dma_device dev_id π₯chan_dma_devβ The channel is using custom/different dma-mapping compared to the parent dma_device π
π SEE ALSO π
Kernel file ./include/linux/dmaengine.h β go peek, iykyk π¦
dma_cookie_t(9)enum dma_status(9)enum dma_transaction_type(9)enum dma_transfer_direction(9)struct data_chunk(9)struct dma_interleaved_template(9)struct dma_vec(9)enum dma_ctrl_flags(9)enum sum_check_bits(9)enum sum_check_flags(9)enum dma_desc_metadata_mode(9)struct dma_chan_percpu(9)struct dma_router(9)struct dma_chan(9)enum dma_slave_buswidth(9)struct dma_slave_config(9)enum dma_residue_granularity(9)struct dma_slave_caps(9)dma_filter_fn(9)struct dma_async_tx_descriptor(9)struct dma_tx_state(9)enum dmaengine_alignment(9)struct dma_slave_map(9)struct dma_filter(9)struct dma_device(9)dmaengine_prep_peripheral_dma_vec(9)dmaengine_prep_config_sg_safe(9)dmaengine_prep_config_single_safe(9)dmaengine_prep_dma_memset(9)dmaengine_terminate_all(9)dmaengine_terminate_async(9)dmaengine_synchronize(9)dmaengine_terminate_sync(9)dma_async_issue_pending(9)dma_async_is_tx_complete(9)dma_async_is_complete(9)
okay thatβs the whole page bestie π«Ά source/version: ./include/linux, date: October 2026, page: struct dma_chan_dev(9) β mwah π
π¦ 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