| /openbmc/u-boot/doc/ |
| H A D | README.davinci | 4 This README is about U-Boot support for TI's ARM 926EJS based family of SoCs.
9 Additionally, some family members contain a TI DSP and/or graphics
14 * TI DaVinci DM644x EVM
16 * TI DaVinci DM646x EVM
18 * TI DaVinci DM355 EVM
20 * TI DaVinci DM365 EVM
22 * TI DA830 EVM
24 * TI DA850 EVM
37 * TI DaVinci DM644x EVM:
42 * TI DaVinci DM646x EVM:
[all …]
|
| H A D | README.omap3 | 5 This README is about U-Boot support for TI's ARM Cortex-A8 based OMAP3 [1]
6 family of SoCs. TI's OMAP3 SoC family contains an ARM Cortex-A8. Additionally,
16 * TI EVM [4]
20 * TI/Logic PD Zoom MDK [6]
22 * TI/Logic PD Zoom 2 [7]
39 * TI EVM:
169 several TI employees.
187 [4] TI EVM:
195 [6] TI/Logic PD Zoom MDK:
199 [7] TI/Logic PD Zoom 2
[all …]
|
| /openbmc/linux/drivers/net/ethernet/ti/ |
| H A D | Kconfig | 3 # TI device configuration
7 bool "Texas Instruments (TI) devices"
15 the questions about TI devices. If you say Y, you will be asked for
21 tristate "TI DaVinci EMAC Support"
27 This driver supports TI's DaVinci Ethernet .
33 tristate "TI DaVinci MDIO Support"
38 This driver supports TI's DaVinci MDIO module.
44 bool "TI CPSW Phy mode Selection (DEPRECATED)"
51 tristate "TI CPSW Switch Support"
60 This driver supports TI's CPSW Ethernet Switch.
[all …]
|
| /openbmc/u-boot/drivers/net/ti/ |
| H A D | Kconfig | 6 bool "TI Common Platform Ethernet Switch"
9 This driver supports the TI three port switch gigabit ethernet
10 subsystem found in the TI SoCs.
13 bool "TI Davinci EMAC"
18 bool "TI Keystone 2 Ethernet"
20 This driver supports the TI Keystone 2 Ethernet subsystem
|
| /openbmc/linux/drivers/soc/ti/ |
| H A D | Kconfig | 4 # TI SOC drivers
7 bool "TI SOC drivers support"
24 tristate "TI Keystone Navigator Packet DMA support"
44 tristate "TI AMx3 Wkup-M3 IPC Driver"
48 TI AM33XX and AM43XX have a Cortex M3, the Wakeup M3, to handle
54 tristate "TI SCI PM Domains Driver"
58 Generic power domain implementation for TI device implementing
59 the TI SCI protocol.
73 and a consumer. There is one RINGACC module per NAVSS on TI AM65x SoCs
82 Include support for the SoC bus socinfo for the TI K3 Multicore SoC
[all …]
|
| /openbmc/linux/drivers/phy/ti/ |
| H A D | Kconfig | 3 # Phy drivers for TI platforms
6 tristate "TI DA8xx USB PHY Driver"
16 tristate "TI dm816x USB PHY driver"
25 tristate "TI AM654 SERDES support"
33 This option enables support for TI AM654 SerDes PHY used for
37 tristate "TI J721E WIZ (SERDES Wrapper) support"
46 This option enables support for WIZ module present in TI's J721E
77 tristate "TI PIPE3 PHY Driver"
82 Enable this to support the PIPE3 PHY that is part of TI SOCs. This
88 tristate "TI TUSB1210 ULPI PHY module"
[all …]
|
| /openbmc/u-boot/drivers/remoteproc/ |
| H A D | Kconfig | 17 bool "Support for TI' K3 System Controller"
23 Say 'y' here to add support for TI' K3 System Controller.
26 bool "Support for TI's K3 based remoteproc driver"
32 Say 'y' here to add support for TI' K3 remoteproc driver.
44 bool "Support for TI Power processor"
50 Say 'y' here to add support for TI power processors such as those
51 found on certain TI keystone and OMAP generation SoCs.
|
| /openbmc/u-boot/arch/arm/mach-keystone/ |
| H A D | Kconfig | 4 prompt "TI Keystone board select"
8 bool "TI Keystone 2 Kepler/Hawking EVM"
14 bool "TI Keystone 2 Edison EVM"
20 bool "TI Keystone 2 Lamar EVM"
26 bool "TI Keystone 2 Galileo EVM"
|
| /openbmc/linux/drivers/net/wireless/ti/wl1251/ |
| H A D | Kconfig | 3 tristate "TI wl1251 driver support"
8 This will enable TI wl1251 driver support. The drivers make
15 tristate "TI wl1251 SPI support"
19 TI wl1251 chipset. Select this if your platform is using
26 tristate "TI wl1251 SDIO support"
30 TI wl1251 chipset. Select this if your platform is using
|
| /openbmc/linux/drivers/net/wireless/ti/wlcore/ |
| H A D | Kconfig | 3 tristate "TI wlcore support"
7 This module contains the main code for TI WLAN chips. It abstracts
16 tristate "TI wlcore SPI support"
21 TI WLAN chipsets. Select this if your platform is using
28 tristate "TI wlcore SDIO support"
32 TI WLAN chipsets. Select this if your platform is using
|
| /openbmc/linux/Documentation/admin-guide/media/ |
| H A D | platform-cardlist.rst | 17 am437x-vpfe TI AM437x VPFE
27 dm355_ccdc TI DM355 CCDC video capture
28 dm644x_ccdc TI DM6446 CCDC video capture
34 isdf TI DM365 ISIF video capture
67 ti-cal TI Memory-to-memory multimedia devices
68 ti-csc TI DVB platform devices
69 ti-vpe TI VPE (Video Processing Engine)
73 vpif_display TI DaVinci VPIF V4L2-Display
74 vpif_capture TI DaVinci VPIF video capture
|
| /openbmc/linux/drivers/media/platform/ti/ |
| H A D | Kconfig | 5 # TI VIDEO PORT Helper Modules
19 tristate "TI CAL (Camera Adaptation Layer) driver"
28 Support for the TI CAL (Camera Adaptation Layer) block
30 In TI Technical Reference Manual this module is referred as
47 tristate "TI VPE (Video Processing Engine) driver"
57 Support for the TI VPE(Video Processing Engine) block
|
| /openbmc/linux/drivers/pci/controller/cadence/ |
| H A D | Kconfig | 49 bool "TI J721E PCIe controller (host mode)"
54 Say Y here if you want to support the TI J721E PCIe platform
55 controller in host mode. TI J721E PCIe controller uses Cadence PCIe
59 bool "TI J721E PCIe controller (endpoint mode)"
65 Say Y here if you want to support the TI J721E PCIe platform
66 controller in endpoint mode. TI J721E PCIe controller uses Cadence PCIe
|
| /openbmc/u-boot/doc/device-tree-bindings/sysreset/ |
| H A D | ti,sci-sysreset.txt | 1 Texas Instruments TI SCI System Reset Controller
4 Some TI SoCs contain a system controller (like the SYSFW, etc...) that is
7 controller happens through a protocol known as TI SCI [1].
14 which is managed by the SYSFW. Because this relies on the TI SCI protocol
|
| /openbmc/openpower-hw-diags/attn/ |
| H A D | Attention_Handler.md | 28 priority, Vital Attention (vital), Terminate Immediately (TI), Breakpoint
29 Attention (BP) and Checkstop Attention (checkstop). TI and BP attentions are
31 Additionally a TI can be raised by either hostboot (HBTI) or the hypervisor
104 a portion of shared memory called the Shared TI Information Data Area (TI info).
113 will consider two cases namely a TI with SRC and a TI with EID.
115 For a TI with SRC, using the TI info, the attention handler will create and
118 Optionally, based upon flags in the TI info, the attention handler may mark the
121 For a TI with EID, the attention handler will, based upon flags in the TI info,
124 interface. For a TI with EID the attention handler will forgo creating a PEL
137 encountered. If the TI info data is considered valid and neither a HBTI or
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/firmware/ |
| H A D | ti,sci.txt | 1 Texas Instruments System Control Interface (TI-SCI) Message Protocol
16 TI-SCI controller Device Node:
19 The TI-SCI node describes the Texas Instrument's System Controller entity node.
23 relationship between the TI-SCI parent node to the child node.
56 TI-SCI Client Device Node:
59 Client nodes are maintained as children of the relevant TI-SCI device node.
|
| /openbmc/u-boot/doc/device-tree-bindings/reset/ |
| H A D | ti,sci-reset.txt | 1 Texas Instruments TI SCI Reset Controller
4 Some TI SoCs contain a system controller (like the SYSFW, etc...) that is
7 controller happens through a protocol known as TI SCI [1].
14 present on the SoC managed by the SYSFW. Because this relies on the TI SCI
43 should point to the TI SCI reset controller node, and the reset
|
| /openbmc/linux/drivers/media/platform/ti/davinci/ |
| H A D | Kconfig | 3 tristate "TI DaVinci VPIF V4L2-Display driver"
13 This module is used for display on TI DM6467/DA850/OMAPL138
20 tristate "TI DaVinci VPIF video capture driver"
29 This module is used for capture on TI DM6467/DA850/OMAPL138
|
| /openbmc/linux/drivers/gpu/drm/tidss/ |
| H A D | Kconfig | 2 tristate "DRM Support for TI Keystone"
8 The TI Keystone family SoCs introduced a new generation of
12 or M to add display support for TI Keystone family
|
| /openbmc/linux/drivers/clk/keystone/ |
| H A D | Kconfig | 10 tristate "TI System Control Interface clock drivers"
15 This adds the clock driver support over TI System Control Interface.
24 Forces the TI SCI clock driver to probe available clocks from the
36 clocks on TI's K2 and K3 SoCs.
|
| /openbmc/linux/arch/arm/mach-omap2/ |
| H A D | Kconfig | 2 menu "TI OMAP/AM/DM/DRA Family"
9 bool "TI OMAP2"
17 bool "TI OMAP3"
28 bool "TI OMAP4"
48 bool "TI OMAP5"
62 bool "TI AM33XX"
68 bool "TI AM43x"
82 bool "TI DRA7XX"
132 menu "TI OMAP2/3/4 Specific Features"
|
| /openbmc/u-boot/drivers/firmware/ |
| H A D | Kconfig | 13 tristate "TI System Control Interface (TISCI) Message Protocol"
17 TI System Control Interface (TISCI) Message Protocol is used to manage
20 generation SoC from TI.
|
| /openbmc/linux/drivers/dma/ti/ |
| H A D | Kconfig | 22 Enable support for the TI EDMA (Enhanced DMA) controller. This DMA
23 engine is found on TI DaVinci, AM33xx, AM43xx, DRA7xx and Keystone 2
34 Enable support for the TI sDMA (System DMA or DMA4) controller. This
47 Enable support for the TI UDMA (Unified DMA) controller. This
|
| /openbmc/u-boot/doc/device-tree-bindings/power/ |
| H A D | ti,sci-pm-domain.txt | 1 Texas Instruments TI SCI Generic Power Domain
4 Some TI SoCs contain a system controller (like the SYSFW, etc...) that is
7 controller happens through a protocol known as TI SCI [1].
14 this relies on the TI SCI protocol to communicate with the SYSFW it must be a
|
| /openbmc/u-boot/doc/device-tree-bindings/clock/ |
| H A D | ti,sci-clk.txt | 1 Texas Instruments TI SCI Clock Controller
7 as TI SCI[1]. This clock implementation plugs into the common clock
8 framework and makes use of the TI SCI protocol on clock API requests.
15 this relies on the TI SCI protocol to communicate with the SYSFW it must be a
|