| /openbmc/u-boot/doc/ |
| H A D | README.davinci | 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
47 * TI DaVinci DM355 EVM:
57 * TI DA830 EVM:
62 * TI DA850 EVM:
144 6) TI DA830 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"
21 tristate "TI DaVinci EMAC Support"
33 tristate "TI DaVinci MDIO Support"
51 tristate "TI CPSW Switch Support"
125 tristate "TI K3 AM65x CPTS"
147 tristate "TI Keystone NETCP Core Support"
167 tristate "TI ThunderLAN support"
184 tristate "TI AR7 CPMAC Ethernet support"
188 TI AR7 CPMAC Ethernet support
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/ti/ |
| H A D | omap.yaml | 20 - description: TI OMAP2420 SoC based platforms
30 - description: TI OMAP2430 SoC based platforms
33 - ti,omap2430-sdp # TI OMAP2430 SDP
37 - description: TI OMAP3430 SoC based platforms
76 - description: TI OMAP3630 SoC based platforms
94 - description: TI AM35 SoC based platforms
104 - description: TI AM33 based platform
122 - description: Phytec boards based on TI AM33
131 - description: TI OMAP4430 SoC based platforms
149 - description: TI OMAP4460 SoC based platforms
[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/Documentation/devicetree/bindings/soc/ti/ |
| H A D | sci-pm-domain.yaml | 7 title: TI-SCI generic power domain
16 Some TI SoCs contain a system controller (like the Power Management Micro
20 through a protocol called TI System Control Interface (TI-SCI protocol).
22 This PM domain node represents the global PM domain managed by the TI-SCI
23 controller. Since this relies on the TI SCI protocol to communicate with
24 the TI-SCI controller, it must be a child of the TI-SCI controller node.
33 The two cells represent values that the TI-SCI controller defines.
|
| /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.
87 tristate "TI PRU-ICSS Subsystem Platform drivers"
91 TI PRU-ICSS Subsystem platform specific support.
[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/linux/Documentation/devicetree/bindings/arm/keystone/ |
| H A D | ti,k3-sci-common.yaml | 7 title: Common K3 TI-SCI
13 The TI K3 family of SoCs usually have a central System Controller Processor
16 through the TI-SCI protocol.
21 over the TI-SCI protocol. The following are some of the common properties
29 Should be a phandle to the TI-SCI System Controller node
34 Should contain the TI-SCI device id corresponding to the device. Please
42 - description: TI-SCI processor id for the remote processor device
43 - description: TI-SCI host id to which processor control ownership
|
| H A D | ti,sci.yaml | 7 title: TI-SCI controller
25 The TI-SCI node describes the Texas Instrument's System Controller entity node.
29 relationship between the TI-SCI parent node to the child node.
37 - description: System controller on TI 66AK2G SoC and other K3 SoCs
40 - description: System controller on TI AM654 SoC
47 made available from TI-SCI controller.
55 Specifies the mailboxes used to communicate with TI-SCI Controller
56 made available from TI-SCI controller.
|
| /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/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/Documentation/devicetree/bindings/clock/ |
| H A D | ti,sci-clk.yaml | 7 title: TI-SCI clock controller
13 Some TI SoCs contain a system controller (like the Power Management Micro
17 through a protocol called TI System Control Interface (TI-SCI protocol).
19 This clock controller node uses the TI SCI protocol to perform various clock
21 node must be a child node of the associated TI-SCI system controller node.
33 The two cells represent values that the TI-SCI controller defines.
|
| /openbmc/linux/Documentation/devicetree/bindings/reset/ |
| H A D | ti,sci-reset.yaml | 7 title: TI-SCI reset controller
13 Some TI SoCs contain a system controller (like the Power Management Micro
17 through a protocol called TI System Control Interface (TI-SCI protocol).
19 This reset controller node uses the TI SCI protocol to perform the reset
21 node of the associated TI-SCI system controller node.
33 The two cells represent values that the TI-SCI controller defines.
|
| /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/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/qemu/docs/system/arm/ |
| H A D | nseries.rst | 14 - TI TSC2301 (in N800) and TI TSC2005 (in N810) touchscreen
25 TI TUSB6010 chip - only USB host mode is supported
27 - TI TMP105 temperature sensor driven through |I2C| bus
29 - TI TWL92230C power management companion with an RTC on
|
| /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/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/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/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/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/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
121 For a TI with EID, the attention handler will, based upon flags in the TI info,
137 encountered. If the TI info data is considered valid and neither a HBTI or
148 a TI the attention handler will note whether or not the host is reporting
169 - TI handling enable/disable, default enable
[all …]
|