u-boot/drivers/dma/ti/Makefile

# SPDX-License-Identifier: GPL-2.0+

obj-$(CONFIG_TI_K3_NAVSS_UDMA) += k3-udma.o
obj-$(CONFIG_TI_K3_PSIL) += k3-psil-data.o
k3-psil-data-y += k3-psil.o
k3-psil-data-$(CONFIG_SOC_K3_AM654) += k3-psil-am654.o
k3-psil-data-$(CONFIG_SOC_K3_J721E) += k3-psil-j721e.o
k3-psil-data-$(CONFIG_SOC_K3_J721S2) += k3-psil-j721s2.o
k3-psil-data-$(CONFIG_SOC_K3_AM642) += k3-psil-am64.o
k3-psil-data-$(CONFIG_SOC_K3_AM625) += k3-psil-am62.o
dma: ti: add driver to K3 UDMA The UDMA-P is intended to perform similar (but significantly upgraded) functions as the packet-oriented DMA used on previous SoC devices. The UDMA-P module supports the transmission and reception of various packet types. The UDMA-P also supports acting as both a UTC and UDMA-C for its internal channels. Channels in the UDMA-P can be configured to be either Packet-Based or Third-Party channels on a channel by channel basis. The initial driver supports: - MEM_TO_MEM (TR mode) - DEV_TO_MEM (Packet mode) - MEM_TO_DEV (Packet mode) Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com> Signed-off-by: Vignesh R <vigneshr@ti.com> 2019-02-05 12:01:24 +00:00			`# SPDX-License-Identifier: GPL-2.0+`

			`obj-$(CONFIG_TI_K3_NAVSS_UDMA) += k3-udma.o`
dma: ti: Add static PSIL endpoint information Much of PSIL endpoint configuration for a given SoC can be known at compile time, therefore pass them for platform specific data instead of DT. Add per SoC's specific PSIL endpoint data. This is to bring driver in sync with upstream DT. Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com> Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com> 2020-07-07 08:13:33 +00:00			`obj-$(CONFIG_TI_K3_PSIL) += k3-psil-data.o`
			`k3-psil-data-y += k3-psil.o`
arm: mach-k3: Rename SOC_K3_AM6 to SOC_K3_AM654 The first AM6x device was the AM654x, but being the first we named it just AM6, since more devices have come out with this same prefix we should switch it to the normal convention of using the full name of the first compatibility device the series. This makes what device we are talking about more clear and matches all the K3 devices added since. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> 2022-07-15 15:25:27 +00:00			`k3-psil-data-$(CONFIG_SOC_K3_AM654) += k3-psil-am654.o`
dma: ti: Add static PSIL endpoint information Much of PSIL endpoint configuration for a given SoC can be known at compile time, therefore pass them for platform specific data instead of DT. Add per SoC's specific PSIL endpoint data. This is to bring driver in sync with upstream DT. Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com> Reviewed-by: Grygorii Strashko <grygorii.strashko@ti.com> 2020-07-07 08:13:33 +00:00			`k3-psil-data-$(CONFIG_SOC_K3_J721E) += k3-psil-j721e.o`
drivers: dma: Add support for J721S2 Add support for DMA in J721S2 SoC. Signed-off-by: David Huang <d-huang@ti.com> Signed-off-by: Aswath Govindraju <a-govindraju@ti.com> 2022-01-25 15:26:32 +00:00			`k3-psil-data-$(CONFIG_SOC_K3_J721S2) += k3-psil-j721s2.o`
dma: ti: k3-psil-am64: Add AM64 PSIL endpoint data Add AM64 SoC specific channel mapping and endpoint data. Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com> 2021-05-10 14:36:07 +00:00			`k3-psil-data-$(CONFIG_SOC_K3_AM642) += k3-psil-am64.o`
dma: ti: Add PSIL data for AM62x DMASS Add PSIL data for AM62x SoC. Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com> 2022-05-25 08:08:44 +00:00			`k3-psil-data-$(CONFIG_SOC_K3_AM625) += k3-psil-am62.o`