Home
last modified time | relevance | path

Searched +full:k3 +full:- +full:am654 (Results 1 – 25 of 74) sorted by relevance

123

/openbmc/linux/Documentation/devicetree/bindings/remoteproc/
H A Dti,pru-rproc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,pru-rproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Suman Anna <s-anna@ti.com>
13 Each Programmable Real-Time Unit and Industrial Communication Subsystem
14 (PRU-ICSS or PRUSS) has two 32-bit load/store RISC CPU cores called
15 Programmable Real-Time Units (PRUs), each represented by a node. Each PRU
17 use the Data RAMs present within the PRU-ICSS for code execution.
19 The K3 SoCs containing ICSSG v1.0 (eg: AM65x SR1.0) also have two Auxiliary
[all …]
H A Dti,k3-r5f-rproc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-r5f-rproc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI K3 R5F processor subsystems
10 - Suman Anna <s-anna@ti.com>
13 The TI K3 family of SoCs usually have one or more dual-core Arm Cortex R5F
20 AM64x SoCs do not support LockStep mode, but rather a new non-safety mode
21 called "Single-CPU" mode, where only Core0 is used, but with ability to use
27 Each Dual-Core R5F sub-system is represented as a single DTS node
[all …]
/openbmc/linux/arch/arm64/boot/dts/ti/
H A DMakefile1 # SPDX-License-Identifier: GPL-2.0
6 # Copyright (C) 2016-2021 Texas Instruments Incorporated - https://www.ti.com/
12 k3-am625-sk-hdmi-audio-dtbs := k3-am625-sk.dtb k3-am62x-sk-hdmi-audio.dtbo
13 k3-am62-lp-sk-hdmi-audio-dtbs := k3-am62-lp-sk.dtb k3-am62x-sk-hdmi-audio.dtbo
14 dtb-$(CONFIG_ARCH_K3) += k3-am625-beagleplay.dtb
15 dtb-$(CONFIG_ARCH_K3) += k3-am625-phyboard-lyra-rdk.dtb
16 dtb-$(CONFIG_ARCH_K3) += k3-am625-sk.dtb
17 dtb-$(CONFIG_ARCH_K3) += k3-am625-verdin-nonwifi-dahlia.dtb
18 dtb-$(CONFIG_ARCH_K3) += k3-am625-verdin-nonwifi-dev.dtb
19 dtb-$(CONFIG_ARCH_K3) += k3-am625-verdin-nonwifi-yavia.dtb
[all …]
H A Dk3-am65.dtsi1 // SPDX-License-Identifier: GPL-2.0
5 * Copyright (C) 2016-2018 Texas Instruments Incorporated - https://www.ti.com/
8 #include <dt-bindings/gpio/gpio.h>
9 #include <dt-bindings/interrupt-controller/irq.h>
10 #include <dt-bindings/interrupt-controller/arm-gic.h>
11 #include <dt-bindings/soc/ti,sci_pm_domain.h>
13 #include "k3-pinctrl.h"
16 model = "Texas Instruments K3 AM654 SoC";
17 compatible = "ti,am654";
18 interrupt-parent = <&gic500>;
[all …]
H A Dk3-am6528-iot2050-basic-pg2.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (c) Siemens AG, 2018-2021
9 * AM6528-based (dual-core) IOT2050 Basic variant, Product Generation 2
13 * https://new.siemens.com/global/en/products/automation/pc-based/iot-gateways/simatic-iot2050.html
16 /dts-v1/;
18 #include "k3-am6528-iot2050-basic-common.dtsi"
19 #include "k3-am65-iot2050-common-pg2.dtsi"
22 compatible = "siemens,iot2050-basic-pg2", "ti,am654";
H A Dk3-am6548-iot2050-advanced.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (c) Siemens AG, 2018-2021
9 * AM6548-based (quad-core) IOT2050 Advanced variant, Product Generation 1
10 * 2 GB RAM, 16 GB eMMC, USB-serial converter on connector X30
13 * https://new.siemens.com/global/en/products/automation/pc-based/iot-gateways/simatic-iot2050.html
16 /dts-v1/;
18 #include "k3-am6548-iot2050-advanced-common.dtsi"
19 #include "k3-am65-iot2050-common-pg1.dtsi"
22 compatible = "siemens,iot2050-advanced", "ti,am654";
H A Dk3-am6528-iot2050-basic.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (c) Siemens AG, 2018-2021
9 * AM6528-based (dual-core) IOT2050 Basic variant, Product Generation 1
13 * https://new.siemens.com/global/en/products/automation/pc-based/iot-gateways/simatic-iot2050.html
16 /dts-v1/;
18 #include "k3-am6528-iot2050-basic-common.dtsi"
19 #include "k3-am65-iot2050-common-pg1.dtsi"
22 compatible = "siemens,iot2050-basic", "ti,am654";
H A Dk3-am6548-iot2050-advanced-pg2.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (c) Siemens AG, 2018-2021
9 * AM6548-based (quad-core) IOT2050 Advanced variant, Product Generation 2
10 * 2 GB RAM, 16 GB eMMC, USB-serial converter on connector X30
13 * https://new.siemens.com/global/en/products/automation/pc-based/iot-gateways/simatic-iot2050.html
16 /dts-v1/;
18 #include "k3-am6548-iot2050-advanced-common.dtsi"
19 #include "k3-am65-iot2050-common-pg2.dtsi"
22 compatible = "siemens,iot2050-advanced-pg2", "ti,am654";
27 /* lock-step mode not supported on this board */
[all …]
/openbmc/u-boot/arch/arm/dts/
H A Dk3-am654-r5-base-board.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2016-2018 Texas Instruments Incorporated - http://www.ti.com/
6 /dts-v1/;
8 #include "k3-am654.dtsi"
9 #include "k3-am654-base-board-u-boot.dtsi"
10 #include "k3-am654-base-board-ddr4-1600MHz.dtsi"
11 #include "k3-am654-ddr.dtsi"
14 compatible = "ti,am654-evm", "ti,am654";
15 model = "Texas Instruments AM654 R5 Base Board";
23 stdout-path = "serial2:115200n8";
[all …]
H A Dk3-am65.dtsi1 // SPDX-License-Identifier: GPL-2.0
5 * Copyright (C) 2016-2018 Texas Instruments Incorporated - http://www.ti.com/
8 #include <dt-bindings/gpio/gpio.h>
9 #include <dt-bindings/interrupt-controller/irq.h>
10 #include <dt-bindings/interrupt-controller/arm-gic.h>
13 model = "Texas Instruments K3 AM654 SoC";
14 compatible = "ti,am654";
15 interrupt-parent = <&gic500>;
16 #address-cells = <2>;
17 #size-cells = <2>;
[all …]
H A Dk3-am654-base-board.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2016-2018 Texas Instruments Incorporated - http://www.ti.com/
6 /dts-v1/;
8 #include "k3-am654.dtsi"
11 compatible = "ti,am654-evm", "ti,am654";
12 model = "Texas Instruments AM654 Base Board";
15 stdout-path = "serial2:115200n8";
26 reserved-memory {
27 #address-cells = <2>;
28 #size-cells = <2>;
[all …]
/openbmc/linux/Documentation/devicetree/bindings/arm/ti/
H A Dk3.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/arm/ti/k3.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Texas Instruments K3 Multicore SoC architecture
10 - Nishanth Menon <nm@ti.com>
13 Platforms based on Texas Instruments K3 Multicore SoC architecture
22 - description: K3 AM62A7 SoC
24 - enum:
25 - ti,am62a7-sk
[all …]
/openbmc/u-boot/board/ti/am65x/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0+
3 # Copyright (C) 2017-2018 Texas Instruments Incorporated - http://www.ti.com/
7 prompt "K3 AM65 based boards"
11 bool "TI K3 based AM654 EVM running on A53"
16 bool "TI K3 based AM654 EVM running on R5"
50 default "arch/arm/mach-omap2/u-boot-spl.lds"
/openbmc/linux/Documentation/devicetree/bindings/hwinfo/
H A Dti,k3-socinfo.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/hwinfo/ti,k3-socinfo.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Texas Instruments K3 Multicore SoC platforms chipid module
10 - Tero Kristo <t-kristo@ti.com>
11 - Nishanth Menon <nm@ti.com>
14 Texas Instruments (ARM64) K3 Multicore SoC platforms chipid module is
20 pattern: "^chipid@[0-9a-f]+$"
24 - const: ti,am654-chipid
[all …]
/openbmc/u-boot/doc/device-tree-bindings/memory-controllers/
H A Dk3-am654-ddrss.txt1 Texas Instruments' K3 AM654 DDRSS
4 K3 based AM654 devices has DDR memory subsystem that comprises
15 --------------------
16 - compatible: Shall be: "ti,am654-ddrss"
17 - reg-names ss - Map the sub system wrapper logic region
18 ctl - Map the controller region
19 phy - Map the PHY region
20 - reg: Contains the register map per reg-names.
21 - power-domains: Should contain a phandle to a PM domain provider node
24 doc/device-tree-bindings/power/ti,sci-pm-domain.txt
[all …]
/openbmc/linux/drivers/dma/ti/
H A DMakefile1 # SPDX-License-Identifier: GPL-2.0
2 obj-$(CONFIG_TI_CPPI41) += cppi41.o
3 obj-$(CONFIG_TI_EDMA) += edma.o
4 obj-$(CONFIG_DMA_OMAP) += omap-dma.o
5 obj-$(CONFIG_TI_K3_UDMA) += k3-udma.o
6 obj-$(CONFIG_TI_K3_UDMA_GLUE_LAYER) += k3-udma-glue.o
7 k3-psil-lib-objs := k3-psil.o \
8 k3-psil-am654.o \
9 k3-psil-j721e.o \
10 k3-psil-j7200.o \
[all …]
/openbmc/u-boot/doc/device-tree-bindings/remoteproc/
H A Dk3-system-controller.txt1 Texas Instruments' K3 System Controller
4 K3 specific SoCs have a dedicated microcontroller for doing
10 --------------------
11 - compatible: Shall be: "ti,am654-system-controller"
12 - mbox-names: "tx" for Transfer channel
14 - mboxes: Corresponding phandles to mailbox channels.
18 --------
20 system-controller: system-controller {
21 compatible = "ti,am654-system-controller";
23 mbox-names = "tx", "rx";
H A Dk3-rproc.txt1 Texas Instruments' K3 Remote processor driver
4 In K3 generation Socs, loading an image on any processing entity
5 cannot be done directly from U-Boot. In order to load an image,
10 --------------------
11 - compatible: Shall be: "ti,am654-rproc"
12 - reg: base address of the remoteproc timer.
13 - power-domains: Should contain two sets of entries:
18 doc/device-tree-bindings/power/ti,sci-pm-domain.txt
19 - resets: Should contain a phandle to a reset controller node
22 doc/device-tree-bindings/reset/ti,sci-reset.txt
[all …]
/openbmc/linux/Documentation/devicetree/bindings/soc/ti/
H A Dk3-ringacc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
2 # Copyright (C) 2020 Texas Instruments Incorporated - http://www.ti.com/
4 ---
5 $id: http://devicetree.org/schemas/soc/ti/k3-ringacc.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Texas Instruments K3 NavigatorSS Ring Accelerator
11 - Santosh Shilimkar <ssantosh@kernel.org>
12 - Grygorii Strashko <grygorii.strashko@ti.com>
26 management of the packet queues. The K3 SoCs can have more than one RA instances
29 - $ref: /schemas/arm/keystone/ti,k3-sci-common.yaml#
[all …]
/openbmc/u-boot/doc/device-tree-bindings/mailbox/
H A Dk3-secure-proxy.txt1 Texas Instruments' K3 Secure Proxy
4 The Texas Instruments' K3 Secure Proxy is a mailbox controller that has
11 --------------------
12 - compatible: Shall be: "ti,am654-secure-proxy"
13 - reg-names data - Map the data region
14 scfg - Map the secure configuration region
15 rt - Map the Realtime region.
16 - reg: Contains the register map per reg-names.
17 - #mbox-cells Shall be 1. Contains the thread ID.
20 --------
[all …]
/openbmc/u-boot/include/configs/
H A Dam65x_evm.h1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * Configuration header file for K3 AM654 EVM
5 * Copyright (C) 2017-2018 Texas Instruments Incorporated - http://www.ti.com/
38 CONFIG_SYS_K3_NON_SECURE_MSRAM_SIZE - 4)
42 /* U-Boot general configuration */
46 "setenv name_fdt k3-am654-base-board.dtb; " \
58 /* U-Boot MMC-specific configuration */
64 "rd_spec=-\0" \
70 /* Incorporate settings into the U-Boot environment */
/openbmc/linux/Documentation/devicetree/bindings/dma/ti/
H A Dk3-udma.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
5 ---
6 $id: http://devicetree.org/schemas/dma/ti/k3-udma.yaml#
7 $schema: http://devicetree.org/meta-schemas/core.yaml#
9 title: Texas Instruments K3 NAVSS Unified DMA
12 - Peter Ujfalusi <peter.ujfalusi@gmail.com>
15 The UDMA-P is intended to perform similar (but significantly upgraded)
16 functions as the packet-oriented DMA used on previous SoC devices. The UDMA-P
18 The UDMA-P architecture facilitates the segmentation and reassembly of SoC DMA
29 on the Rx PSI-L interface.
[all …]
/openbmc/linux/Documentation/devicetree/bindings/hwlock/
H A Dti,omap-hwspinlock.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/hwlock/ti,omap-hwspinlock.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI HwSpinlock for OMAP and K3 based SoCs
10 - Suman Anna <s-anna@ti.com>
15 - ti,omap4-hwspinlock # for OMAP44xx, OMAP54xx, AM33xx, AM43xx, DRA7xx SoCs
16 - ti,am64-hwspinlock # for K3 AM64x SoCs
17 - ti,am654-hwspinlock # for K3 AM65x, J721E and J7200 SoCs
22 "#hwlock-cells":
[all …]
/openbmc/linux/Documentation/devicetree/bindings/mtd/
H A Dti,am654-hbmc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mtd/ti,am654-hbmc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: HyperBus Memory Controller (HBMC) on TI's K3 family of SoCs
10 - Vignesh Raghavendra <vigneshr@ti.com>
14 const: ti,am654-hbmc
19 power-domains: true
20 '#address-cells': true
21 '#size-cells': true
[all …]
/openbmc/linux/Documentation/devicetree/bindings/mailbox/
H A Dti,omap-mailbox.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mailbox/ti,omap-mailbox.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: TI OMAP2+ and K3 Mailbox devices
10 - Suman Anna <s-anna@ti.com>
35 lines can also be routed to different processor sub-systems on DRA7xx as they
37 K3 AM65x, J721E and J7200 SoCs has each of these instances form a cluster and
49 within a SoC. The sub-mailboxes (actual communication channels) are
56 "mbox-names" (please see Documentation/devicetree/bindings/mailbox/mailbox.txt
[all …]

123