Searched full:am64x (Results 1 – 17 of 17) sorted by relevance
/openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
H A D | ti,pru-rproc.yaml | 41 - ti,am642-pru # for PRUs in K3 AM64x SoC family 42 - ti,am642-rtu # for RTUs in K3 AM64x SoC family 43 - ti,am642-tx-pru # for Tx_PRUs in K3 AM64x SoC family
|
H A D | ti,k3-r5f-rproc.yaml | 20 AM64x SoCs do not support LockStep mode, but rather a new non-safety mode 75 For AM64x SoCs,
|
/openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | ti,pruss-intc.yaml | 49 Use "ti,icssg-intc" for K3 AM65x, J721E and AM64x family of SoCs 98 - AM64x SoCs have all the 8 host interrupts connected to various
|
/openbmc/linux/arch/arm64/boot/dts/ti/ |
H A D | k3-am64-main.dtsi | 1268 firmware-name = "am64x-pru0_0-fw"; 1277 firmware-name = "am64x-rtu0_0-fw"; 1286 firmware-name = "am64x-txpru0_0-fw"; 1295 firmware-name = "am64x-pru0_1-fw"; 1304 firmware-name = "am64x-rtu0_1-fw"; 1313 firmware-name = "am64x-txpru0_1-fw"; 1409 firmware-name = "am64x-pru1_0-fw"; 1418 firmware-name = "am64x-rtu1_0-fw"; 1427 firmware-name = "am64x-txpru1_0-fw"; 1436 firmware-name = "am64x-pru1_1-fw"; [all …]
|
H A D | k3-am64-phycore-som.dtsi | 10 * https://www.phytec.com/product/phycore-am64x 18 model = "PHYTEC phyCORE-AM64x";
|
H A D | k3-am642-phyboard-electra-rdk.dts | 10 * https://www.phytec.com/product/phyboard-am64x 28 model = "PHYTEC phyBOARD-Electra-AM64x RDK";
|
H A D | Makefile | 33 # Boards with AM64x SoC
|
/openbmc/linux/Documentation/devicetree/bindings/hwlock/ |
H A D | ti,omap-hwspinlock.yaml | 16 - ti,am64-hwspinlock # for K3 AM64x SoCs
|
/openbmc/linux/drivers/remoteproc/ |
H A D | ti_k3_r5_remoteproc.c | 44 /* Applicable to only AM64x SoCs */ 55 /* Applicable to only AM64x SoCs */ 75 * Split mode : AM65x, J721E, J7200 and AM64x SoCs 77 * Single-CPU mode : AM64x SoCs only 439 * The Single-CPU mode on applicable SoCs (eg: AM64x) only uses Core0 to 507 * The Single-CPU mode on applicable SoCs (eg: AM64x) combines the TCMs from 544 * The Single-CPU mode on applicable SoCs (eg: AM64x) only uses Core0 to execute 614 * The Single-CPU mode on applicable SoCs (eg: AM64x) only uses Core0 to execute 1068 * AM64x SoCs). This is done by making a Core1 TCM visible immediately after the 1760 * default to most common efuse configurations - Split-mode on AM64x in k3_r5_probe() [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/mailbox/ |
H A D | ti,omap-mailbox.yaml | 41 output lines of an Interrupt Router. The AM64x SoCS also uses a single IP 123 - ti,am64-mailbox # for K3 AM64x SoCs
|
/openbmc/linux/drivers/dma/ti/ |
H A D | k3-psil.c | 24 { .family = "AM64X", .data = &am64_ep_map },
|
H A D | k3-udma.c | 4445 { .family = "AM64X", .data = &am64_soc_data },
|
/openbmc/linux/drivers/soc/ti/ |
H A D | k3-socinfo.c | 43 { 0xBB38, "AM64X" },
|
/openbmc/linux/Documentation/devicetree/bindings/soc/ti/ |
H A D | ti,pruss.yaml | 69 - ti,am642-icssg # for K3 AM64x SoC family 239 AM437x, AM57xx & 66AK2G SoCs) or 2 IEPs (on K3 AM65x, J721E & AM64x SoCs).
|
/openbmc/linux/drivers/net/ethernet/ti/ |
H A D | davinci_mdio.c | 515 { .family = "AM64X", .revision = "SR1.0", .data = &am65_mdio_soc_data }, 516 { .family = "AM64X", .revision = "SR2.0", .data = &am65_mdio_soc_data },
|
H A D | cpsw_ale.c | 210 /* K3 j721e/j7200 cpsw9g/5g, am64x cpsw3g */
|
/openbmc/linux/drivers/mmc/host/ |
H A D | Kconfig | 1052 support present in TI's AM65x/AM64x/AM62x/J721E SOCs. The controller
|