| /linux/Documentation/devicetree/bindings/dma/ti/ |
| H A D | k3-udma.yaml | 9 title: Texas Instruments K3 NAVSS Unified DMA
35 All transfers within NAVSS is done between PSI-L source and destination
66 - ti,am654-navss-main-udmap
67 - ti,am654-navss-mcu-udmap
68 - ti,j721e-navss-main-udmap
69 - ti,j721e-navss-mcu-udmap
158 cbass_main_navss: navss@30800000 {
169 compatible = "ti,am654-navss-main-udmap";
|
| /linux/arch/arm64/boot/dts/ti/ |
| H A D | k3-j7200.dtsi | 118 <0x00 0x30000000 0x00 0x30000000 0x00 0x0c400000>, /* MAIN NAVSS */
143 ranges = <0x00 0x28380000 0x00 0x28380000 0x00 0x03880000>, /* MCU NAVSS*/
150 <0x00 0x45100000 0x00 0x45100000 0x00 0x00c24000>, /* MMRs, remaining NAVSS */
|
| H A D | k3-j7200-mcu-wakeup.dtsi | 339 compatible = "ti,am654-navss-ringacc";
355 compatible = "ti,j721e-navss-mcu-udmap";
|
| H A D | k3-j7200-main.dtsi | 268 compatible = "ti,am654-navss-ringacc";
283 compatible = "ti,j721e-navss-main-udmap";
|
| H A D | k3-j721s2-main.dtsi | 1068 compatible = "ti,am654-navss-ringacc";
1083 compatible = "ti,j721e-navss-main-udmap";
|
| H A D | k3-j721e-main.dtsi | 368 compatible = "ti,am654-navss-ringacc";
383 compatible = "ti,j721e-navss-main-udmap";
|
| H A D | k3-j784s4-main.dtsi | 1623 compatible = "ti,am654-navss-ringacc";
1638 compatible = "ti,j721e-navss-main-udmap";
|
| /linux/Documentation/devicetree/bindings/soc/ti/ |
| H A D | k3-ringacc.yaml | 34 - const: ti,am654-navss-ringacc
83 compatible = "ti,am654-navss-ringacc";
|
| H A D | keystone-navigator-qmss.txt | 21 : Must be "ti,66ak2g-navss-qm" for QMSS on K2G SoC.
|
| /linux/drivers/dma/ti/ |
| H A D | Kconfig | 55 Say y here to support the K3 NAVSS DMA glue interface
|
| H A D | k3-udma-glue.c | 3 * K3 NAVSS DMA glue interface
1577 MODULE_DESCRIPTION("TI K3 NAVSS DMA glue interface");
|
| H A D | k3-udma.c | 4377 .compatible = "ti,am654-navss-main-udmap",
4381 .compatible = "ti,am654-navss-mcu-udmap",
4384 .compatible = "ti,j721e-navss-main-udmap",
4387 .compatible = "ti,j721e-navss-mcu-udmap",
4540 "ti,am654-navss-main-udmap")) { in udma_setup_resources()
4544 "ti,am654-navss-mcu-udmap")) { in udma_setup_resources()
5371 dev_err(dev, "NAVSS ti,sci-dev-id read failure %d\n", ret); in udma_probe()
|
| /linux/drivers/soc/ti/ |
| H A D | Kconfig | 61 and a consumer. There is one RINGACC module per NAVSS on TI AM65x SoCs
|
| H A D | k3-ringacc.c | 3 * TI K3 NAVSS Ring Accelerator subsystem driver
1458 { .compatible = "ti,am654-navss-ringacc", .data = &k3_ringacc_data, },
|
| /linux/arch/arm/boot/dts/ti/keystone/ |
| H A D | keystone-k2g-netcp.dtsi | 9 compatible = "ti,66ak2g-navss-qm";
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | ti,k3-am654-cpsw-nuss.yaml | 21 and one RX channels and operating by NAVSS Unified DMA Peripheral Root
|
| /linux/Documentation/devicetree/bindings/mailbox/ |
| H A D | ti,omap-mailbox.yaml | 39 NavSS. The interrupt lines from all these clusters are multiplexed and routed
|
| /linux/Documentation/devicetree/bindings/remoteproc/ |
| H A D | ti,k3-r5f-rproc.yaml | 295 ranges = <0x00 0x28380000 0x00 0x28380000 0x00 0x03880000>, /* MCU NAVSS */
|
| /linux/drivers/firmware/ |
| H A D | ti_sci.h | 45 /* NAVSS resource management */
|
| H A D | ti_sci.c | 2051 * ti_sci_cmd_rm_ring_cfg() - Configure a NAVSS ring
|