Searched +full:omap +full:- +full:sub +full:- +full:mailbox (Results 1 – 20 of 20) sorted by relevance
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/mailbox/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/remoteproc/ |
| 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 …]
|
| 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 29 - $ref: /schemas/arm/keystone/ti,k3-sci-common.yaml# [all …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/remoteproc/ |
| 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 …]
|
| 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 29 - $ref: /schemas/arm/keystone/ti,k3-sci-common.yaml# [all …]
|
| 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 Each Dual-Core R5F sub-system is represented as a single DTS node 33 - ti,am654-r5fss 34 - ti,j721e-r5fss 36 power-domains: [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mailbox/ |
| D | omap-mailbox.txt | 1 OMAP2+ and K3 Mailbox 4 The OMAP mailbox hardware facilitates communication between different processors 5 using a queued mailbox interrupt mechanism. The IP block is external to the 10 Each mailbox IP block/cluster has a certain number of h/w fifo queues and output 22 All the current OMAP SoCs except for the newest DRA7xx SoC has a single IP 25 routed to different processor sub-systems on DRA7xx as they are routed through 32 Mailbox Device Node: 34 A Mailbox device node is used to represent a Mailbox IP instance/cluster within 35 a SoC. The sub-mailboxes are represented as child nodes of this parent node. 38 -------------------- [all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/usb/ |
| 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 …]
|
| /kernel/linux/linux-6.6/drivers/crypto/ |
| 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. 131 and uses triple-DES to generate secure random numbers like the 132 ANSI X9.17 standard. User-space programs access the 133 pseudo-random-number device through the char device /dev/prandom. 149 sub-units. One set provides the Modular Arithmetic Unit, 250 This option provides the kernel-side support for the TRNG hardware [all …]
|
| /kernel/linux/linux-5.10/drivers/crypto/ |
| 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. 142 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2). 152 SHA256 secure hash standard (DFIPS 180-2). 194 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3). 206 AES cipher algorithms (FIPS-197). 223 and uses triple-DES to generate secure random numbers like the [all …]
|
| /kernel/linux/linux-6.6/arch/arm/mach-omap2/ |
| 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 …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
| 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" 37 * is driver-specific or driver-kernel integration-specific belongs 116 * debug and emulation sub system [all …]
|
| /kernel/linux/linux-6.6/ |
| 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 …]
|
| 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 ---------- 51 D: in-kernel DRM Maintainer 71 E: tim_alpaerts@toyota-motor-europe.com 75 S: B-2610 Wilrijk-Antwerpen 80 W: http://www-stu.christs.cam.ac.uk/~aia21/ 101 D: Maintainer of ide-cd and Uniform CD-ROM driver, 102 D: ATAPI CD-Changer support, Major 2.1.x CD-ROM update. [all …]
|
| /kernel/linux/linux-5.10/ |
| D | MAINTAINERS | 9 ------------------------- 30 ``diff -u`` to make the patch easy to merge. Be prepared to get your 40 See Documentation/process/coding-style.rst for guidance here. 46 See Documentation/process/submitting-patches.rst for details. 57 include a Signed-off-by: line. The current version of this 59 Documentation/process/submitting-patches.rst. 70 that the bug would present a short-term risk to other users if it 76 Documentation/admin-guide/security-bugs.rst for details. 81 --------------------------------------------------- 97 W: *Web-page* with status/info [all …]
|
| 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 ---------- 51 D: in-kernel DRM Maintainer 71 E: tim_alpaerts@toyota-motor-europe.com 75 S: B-2610 Wilrijk-Antwerpen 80 W: http://www-stu.christs.cam.ac.uk/~aia21/ 101 D: Maintainer of ide-cd and Uniform CD-ROM driver, 102 D: ATAPI CD-Changer support, Major 2.1.x CD-ROM update. [all …]
|
| /kernel/linux/patches/linux-5.10/yangfan_patch/ |
| D | drivers.patch | 1 diff --git a/drivers/Makefile b/drivers/Makefile 3 --- a/drivers/Makefile 5 @@ -6,6 +6,8 @@ 6 # Rewritten to use lists instead of if-statements. 11 obj-y += irqchip/ 12 obj-y += bus/ 14 diff --git a/drivers/block/nbd.c b/drivers/block/nbd.c 16 --- a/drivers/block/nbd.c 18 @@ -2398,12 +2398,6 @@ static int nbd_genl_status(struct sk_buff *skb, struct genl_info *info) 22 - if (!dev_list) { [all …]
|
| /kernel/linux/patches/linux-5.10/imx8mm_patch/patches/drivers/ |
| D | 0020_linux_drivers_gpu.patch | 7 Change-Id: Ie95ebc16d7424b75135df39b9e20893d1a5171d6 9 diff --git a/drivers/gpu/Makefile b/drivers/gpu/Makefile 11 --- a/drivers/gpu/Makefile 13 @@ -3,6 +3,7 @@ 16 obj-$(CONFIG_TEGRA_HOST1X) += host1x/ 17 +obj-y += imx/ 18 obj-y += drm/ vga/ 19 obj-$(CONFIG_IMX_IPUV3_CORE) += ipu-v3/ 20 obj-$(CONFIG_TRACE_GPU_MEM) += trace/ 21 diff --git a/drivers/gpu/drm/Makefile b/drivers/gpu/drm/Makefile [all …]
|