Home
last modified time | relevance | path

Searched full:am64x (Results 1 – 18 of 18) sorted by relevance

/linux-6.8/Documentation/devicetree/bindings/remoteproc/
Dti,pru-rproc.yaml41 - 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
Dti,k3-r5f-rproc.yaml20 AM64x SoCs do not support LockStep mode, but rather a new non-safety mode
75 For AM64x SoCs,
/linux-6.8/Documentation/devicetree/bindings/interrupt-controller/
Dti,pruss-intc.yaml49 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
/linux-6.8/arch/arm64/boot/dts/ti/
Dk3-am64-main.dtsi1282 firmware-name = "am64x-pru0_0-fw";
1291 firmware-name = "am64x-rtu0_0-fw";
1300 firmware-name = "am64x-txpru0_0-fw";
1309 firmware-name = "am64x-pru0_1-fw";
1318 firmware-name = "am64x-rtu0_1-fw";
1327 firmware-name = "am64x-txpru0_1-fw";
1423 firmware-name = "am64x-pru1_0-fw";
1432 firmware-name = "am64x-rtu1_0-fw";
1441 firmware-name = "am64x-txpru1_0-fw";
1450 firmware-name = "am64x-pru1_1-fw";
[all …]
Dk3-am642-phyboard-electra-rdk.dts10 * https://www.phytec.com/product/phyboard-am64x
28 model = "PHYTEC phyBOARD-Electra-AM64x RDK";
Dk3-am64-phycore-som.dtsi10 * https://www.phytec.com/product/phycore-am64x
18 model = "PHYTEC phyCORE-AM64x";
DMakefile39 # Boards with AM64x SoC
/linux-6.8/Documentation/devicetree/bindings/hwlock/
Dti,omap-hwspinlock.yaml16 - ti,am64-hwspinlock # for K3 AM64x SoCs
/linux-6.8/drivers/remoteproc/
Dti_k3_r5_remoteproc.c44 /* 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
430 * The Single-CPU mode on applicable SoCs (eg: AM64x) only uses Core0 to
498 * The Single-CPU mode on applicable SoCs (eg: AM64x) combines the TCMs from
535 * The Single-CPU mode on applicable SoCs (eg: AM64x) only uses Core0 to execute
599 * The Single-CPU mode on applicable SoCs (eg: AM64x) only uses Core0 to execute
1064 * AM64x SoCs). This is done by making a Core1 TCM visible immediately after the
1722 * default to most common efuse configurations - Split-mode on AM64x in k3_r5_probe()
[all …]
/linux-6.8/Documentation/devicetree/bindings/mailbox/
Dti,omap-mailbox.yaml41 output lines of an Interrupt Router. The AM64x SoCS also uses a single IP
123 - ti,am64-mailbox # for K3 AM64x SoCs
/linux-6.8/drivers/dma/ti/
Dk3-psil.c24 { .family = "AM64X", .data = &am64_ep_map },
Dk3-udma.c4445 { .family = "AM64X", .data = &am64_soc_data },
/linux-6.8/Documentation/devicetree/bindings/soc/ti/
Dti,pruss.yaml69 - ti,am642-icssg # for K3 AM64x SoC family
239 AM437x, AM57xx & 66AK2G SoCs) or 2 IEPs (on K3 AM65x, J721E & AM64x SoCs).
/linux-6.8/drivers/soc/ti/
Dk3-socinfo.c54 { JTAG_ID_PARTNO_AM64X, "AM64X" },
/linux-6.8/Documentation/devicetree/bindings/net/
Dti,icssg-prueth.yaml22 - ti,am642-icssg-prueth # for AM64x SoC family
/linux-6.8/drivers/net/ethernet/ti/
Ddavinci_mdio.c515 { .family = "AM64X", .data = &am65_mdio_soc_data },
Dcpsw_ale.c210 /* K3 j721e/j7200 cpsw9g/5g, am64x cpsw3g */
/linux-6.8/drivers/mmc/host/
DKconfig1052 support present in TI's AM65x/AM64x/AM62x/J721E SOCs. The controller