On Mon, Apr 16, 2018 at 02:32:05PM +0800, Baolin Wang wrote: > >> Beside the general configuration, our audio driver will configure the > >> fragment length, block length, maybe transaction length, and they must > >> specify the request type and interrupt type, these are what we want to > >> export for users. > > > > As I said before, you need to derive fragment, block or transaction from > > I am sorry I did not make things clear here. What I mean is not only > link list mode(prep_cyclic), but also other modes (prep_slave, > prep_interleaved ...), users still need to configure the fragment > length, block length or transaction length according to their > requirements. Other modes are similar, they also use the parameters programmed from dma_slave_config. Pls see other driver examples. IIRC dw dma has similar capabilities but not all are exposed to user and driver configures. -- ~Vinod -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
