On Fri, May 08, 2020 at 01:53:03PM +0300, Serge Semin wrote: > IP core of the DW DMA controller may be synthesized with different > max burst length of the transfers per each channel. According to Synopsis > having the fixed maximum burst transactions length may provide some > performance gain. At the same time setting up the source and destination > multi size exceeding the max burst length limitation may cause a serious > problems. In our case the system just hangs up. In order to fix this > lets introduce the max burst length platform config of the DW DMA > controller device and don't let the DMA channels configuration code > exceed the burst length hardware limitation. Depending on the IP core > configuration the maximum value can vary from channel to channel. > It can be detected either in runtime from the DWC parameter registers > or from the dedicated dts property. I'm wondering what can be the scenario when your peripheral will ask something which is not supported by DMA controller? Peripheral needs to supply a lot of configuration parameters specific to the DMA controller in use (that's why we have struct dw_dma_slave). So, seems to me the feasible approach is supply correct data in the first place. If you have specific channels to acquire then you probably need to provide a custom xlate / filter functions. Because above seems a bit hackish workaround of dynamic channel allocation mechanism. But let's see what we can do better. Since maximum is defined on the slave side device, it probably needs to define minimum as well, otherwise it's possible that some hardware can't cope underrun bursts. Vinod, what do you think? -- With Best Regards, Andy Shevchenko
