On 16/01/2025 17:00, Roger Quadros wrote: > The user of k3_udma_glue_reset_rx_chn() e.g. ti_am65_cpsw_nuss can > run on multiple platforms having different DMA architectures. > On some platforms there can be one FDQ for all flows in the RX channel > while for others there is a separate FDQ for each flow in the RX channel. > > So far we have been relying on the skip_fdq argument of > k3_udma_glue_reset_rx_chn(). > > Instead of relying on the user to provide this information, infer it > based on DMA architecture during k3_udma_glue_request_rx_chn() and save it > in an internal flag 'single_fdq'. Use that flag at > k3_udma_glue_reset_rx_chn() to deicide if the FDQ needs > to be cleared for every flow or just for flow 0. This should have been the original approach, there are things that clients must not care. Acked-by: Peter Ujfalusi <peter.ujfalusi@xxxxxxxxx>
