summaryrefslogtreecommitdiffstats
path: root/drivers/ddr/imx/imx8m/ddr_init.c
diff options
context:
space:
mode:
authorVignesh Raghavendra <vigneshr@ti.com>2019-12-04 22:17:21 +0530
committerJoe Hershberger <joe.hershberger@ni.com>2019-12-09 09:47:43 -0600
commit5e6d9ccde9cf700e19e0d783f1f671a1eb4a60fb (patch)
tree1dda58fd65d436618231818ec63a34b28b9f17d8 /drivers/ddr/imx/imx8m/ddr_init.c
parentb8a4dd28f3b719d176fed5dc8d23a898463b072c (diff)
downloadu-boot-5e6d9ccde9cf700e19e0d783f1f671a1eb4a60fb.tar.gz
u-boot-5e6d9ccde9cf700e19e0d783f1f671a1eb4a60fb.tar.xz
u-boot-5e6d9ccde9cf700e19e0d783f1f671a1eb4a60fb.zip
dma: ti: k3-udma: Implement dma_get_cfg() interface
Implement dma_get_cfg() interface to pass flow id information for DMA clients to use. This is needed because on K3 SoCs, CPSW (ethernet) and UDMA (DMA provider) support "flows" within a given RX DMA channel. This allows different network packets to be segregated while using same RX DMA channel. In order for basic ethernet to work, CPSW slave must be aware of the flow ID allocated for the RX channel by the DMA driver. This interface allows CPSW to query flow ID from DMA provider and configure it in CPSW HW. Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com> Acked-by: Joe Hershberger <joe.hershberger@ni.com> Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com>
Diffstat (limited to 'drivers/ddr/imx/imx8m/ddr_init.c')
0 files changed, 0 insertions, 0 deletions