2010/8/9 Sascha Hauer < XXXX@XXXXX.COM >:
> + int (*setup_single)(int channel, dma_addr_t mem, int dma_len>th,
> + unsigned in> dmamode);
> + int (*setup_sg)(int channel, struct sc>tterlist *sg,
> + unsigned int sgcount,>unsigned int dma_length,
> + > unsigned int dmamode); >> + void (*enable)(int channel)>
> + void (*disable)(int channel); >> + int (*request)(enum imx_>ma_prio);
> + void>(*free)(int channel);
> + int num_channels;
This is just getting *so* close to the drivers/dma dmaengine API.
We decided to use the damengine for all our DMA drivers and we
haven't regretted one bit.
There has been some noise about too many drivers stacking up
below arch/arm instead of going to the apropriate subsystem, can't
you atleast contemplate using the dmaengine and help us improve
I sent some patches to Dan which essentially is a single-buffer
(non-sglist) API, which is all I see missing to fit this need.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to XXXX@XXXXX.COM
More majordomo info at http://www.yqcomputer.com/
Please read the FAQ at http://www.yqcomputer.com/