Searched +full:omap +full:- +full:sub +full:- +full:mailbox (Results 1 – 10 of 10) sorted by relevance
/linux/Documentation/devicetree/bindings/mailbox/ |
H A D | ti,omap-mailbox.yaml | 1 # 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> 13 The OMAP Mailbox hardware facilitates communication between different 14 processors using a queued mailbox interrupt mechanism. The IP block is 19 Each mailbox IP block/cluster has a certain number of h/w fifo queues and 32 registers. All the current OMAP SoCs except for the newest DRA7xx SoC has a [all …]
|
/linux/Documentation/devicetree/bindings/remoteproc/ |
H A D | ti,omap-remoteproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/remoteproc/ti,omap-remoteproc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Suman Anna <s-anna@ti.com> 13 The OMAP family of SoCs usually have one or more slave processor sub-systems 14 that are used to offload some of the processor-intensive tasks, or to manage 17 The processor cores in the sub-system are usually behind an IOMMU, and may 18 contain additional sub-modules like Internal RAM and/or ROMs, L1 and/or L2 21 The OMAP SoCs usually have a DSP processor sub-system and/or an IPU processor [all …]
|
H A D | ti,k3-m4f-rproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-m4f-rproc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Hari Nagalla <hnagalla@ti.com> 11 - Mathieu Poirier <mathieu.poirier@linaro.org> 20 $ref: /schemas/arm/keystone/ti,k3-sci-common.yaml# 25 - ti,am64-m4fss 27 power-domains: 30 "#address-cells": [all …]
|
H A D | ti,k3-dsp-rproc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/remoteproc/ti,k3-dsp-rproc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Suman Anna <s-anna@ti.com> 13 The TI K3 family of SoCs usually have one or more TI DSP Core sub-systems 14 that are used to offload some of the processor-intensive tasks or algorithms, 17 These processor sub-systems usually contain additional sub-modules like 23 Each DSP Core sub-system is represented as a single DT node. Each node has a 31 - ti,am62a-c7xv-dsp [all …]
|
H A D | ti,k3-r5f-rproc.yaml | 1 # 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# 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 40 - ti,am62-r5fss [all …]
|
/linux/Documentation/devicetree/bindings/usb/ |
H A D | omap-usb.txt | 1 OMAP GLUE AND OTHER OMAP SPECIFIC COMPONENTS 3 OMAP MUSB GLUE 4 - compatible : Should be "ti,omap4-musb" or "ti,omap3-musb" 5 - ti,hwmods : must be "usb_otg_hs" 6 - multipoint : Should be "1" indicating the musb controller supports 7 multipoint. This is a MUSB configuration-specific setting. 8 - num-eps : Specifies the number of endpoints. This is also a 9 MUSB configuration-specific setting. Should be set to "16" 10 - ram-bits : Specifies the ram address size. Should be set to "12" 11 - interface-type : This is a board specific setting to describe the type of [all …]
|
/linux/drivers/crypto/ |
H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only 39 called padlock-aes. 53 called padlock-sha. 61 Say 'Y' here to use the AMD Geode LX processor on-board AES 65 will be called geode-aes. 87 - A pkey base and API kernel module (pkey.ko) which offers the 89 and the sysfs API and the in-kernel API to the crypto cipher 91 - A pkey pckmo kernel module (pkey-pckmo.ko) which is automatically 94 - A pkey CCA kernel module (pkey-cca.ko) which is automatically 96 - A pkey EP11 kernel module (pkey-ep11.ko) which is automatically [all …]
|
/linux/arch/arm/mach-omap2/ |
H A D | omap_hwmod_3xxx_data.c | 1 // SPDX-License-Identifier: GPL-2.0-only 3 * omap_hwmod_3xxx_data.c - hardware modules present on the OMAP3xxx chips 5 * Copyright (C) 2009-2011 Nokia Corporation 12 * XXX these should be marked initdata for multi-OMAP kernels 15 #include <linux/platform_data/i2c-omap.h> 17 #include <linux/platform_data/hsmmc-omap.h> 25 #include "prm-regbits-34xx.h" 26 #include "cm-regbits-34xx.h" 36 * is driver-specific or driver-kernel integration-specific belongs 115 * debug and emulation sub system [all …]
|
/linux/ |
H A D | MAINTAINERS | 5 --------------------------------------------------- 21 W: *Web-page* with status/info 23 B: URI for where to file *bugs*. A web-page with detailed bug 28 patches to the given subsystem. This is either an in-tree file, 29 or a URI. See Documentation/maintainer/maintainer-entry-profile.rst 46 N: [^a-z]tegra all files whose path contains tegra 64 ---------------- 83 3WARE SAS/SATA-RAID SCSI DRIVERS (3W-XXXX, 3W-9XXX, 3W-SAS) 85 L: linux-scsi@vger.kernel.org 88 F: drivers/scsi/3w-* [all …]
|
H A D | CREDITS | 1 This is at least a partial credits-file of people that have 4 scripts. The fields are: name (N), email (E), web-address 6 snail-mail address (S). 10 ---------- 47 D: in-kernel DRM Maintainer 72 E: tim_alpaerts@toyota-motor-europe.com 76 S: B-2610 Wilrijk-Antwerpen 81 W: http://www-stu.christs.cam.ac.uk/~aia21/ 102 D: Maintainer of ide-cd and Uniform CD-ROM driver, 103 D: ATAPI CD-Changer support, Major 2.1.x CD-ROM update. [all …]
|