Home
last modified time | relevance | path

Searched +full:processor +full:- +full:intensive (Results 1 – 13 of 13) sorted by relevance

/Linux-v5.10/Documentation/devicetree/bindings/remoteproc/
Dti,davinci-rproc.txt4 Binding status: Unstable - Subject to changes for DT representation of clocks
7 The TI Davinci family of SoCs usually contains a TI DSP Core sub-system that
8 is used to offload some of the processor-intensive tasks or algorithms, for
11 The processor cores in the sub-system usually contain additional sub-modules
13 controller, a dedicated local power/sleep controller etc. The DSP processor
18 Each DSP Core sub-system is represented as a single DT node.
21 --------------------
24 - compatible: Should be one of the following,
25 "ti,da850-dsp" for DSPs on OMAP-L138 SoCs
27 - reg: Should contain an entry for each value in 'reg-names'.
[all …]
Dti,k3-dsp-rproc.yaml1 # 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
19 controller, a dedicated local power/sleep controller etc. The DSP processor
20 cores in the K3 SoCs are usually either a TMS320C66x CorePac processor or a
[all …]
Dti,keystone-rproc.txt5 sub-systems that are used to offload some of the processor-intensive tasks or
8 These processor sub-systems usually contain additional sub-modules like L1
10 a dedicated local power/sleep controller etc. The DSP processor core in
11 Keystone 2 SoCs is usually a TMS320C66x CorePac processor.
15 Each DSP Core sub-system is represented as a single DT node, and should also
17 or optional properties that enable the OS running on the host processor (ARM
18 CorePac) to perform the device management of the remote processor and to
19 communicate with the remote processor.
22 --------------------
25 - compatible: Should be one of the following,
[all …]
Dti,omap-remoteproc.yaml1 # 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 …]
/Linux-v5.10/Documentation/staging/
Drpmsg.rst2 Remote Processor Messaging (rpmsg) Framework
14 Modern SoCs typically employ heterogeneous remote processor devices in
17 flavor of real-time OS.
19 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
20 Typically, the dual cortex-A9 is running Linux in a SMP configuration,
25 hardware accelerators, and therefore are often used to offload CPU-intensive
26 multimedia tasks from the main application processor.
28 These remote processors could also be used to control latency-sensitive
34 hardware accessible only by the remote processor, reserving kernel-controlled
35 resources on behalf of the remote processor, etc..).
[all …]
/Linux-v5.10/Documentation/locking/
Dhwspinlock.rst12 For example, OMAP4 has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP,
17 A generic hwspinlock framework allows platform-independent drivers to use
22 This is necessary, for example, for Inter-processor communications:
23 on OMAP4, cpu-intensive multimedia tasks are offloaded by the host to the
26 To achieve fast message-based communications, a minimal kernel support
27 is needed to deliver messages arriving from a remote processor to the
32 module (remote processor directly places new messages in this shared data
35 A common hwspinlock interface makes it possible to have generic, platform-
67 Retrieve the global lock id for an OF phandle-based specific lock.
72 The function returns a lock id number on success, -EPROBE_DEFER if
[all …]
/Linux-v5.10/drivers/mtd/nand/raw/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
21 <http://www.linux-mtd.infradead.org/doc/nand.html>.
31 codes are more powerful and cpu intensive than traditional Hamming
152 The CS553x companion chips for the AMD Geode processor
153 include NAND flash controllers with built-in hardware ECC
188 - PXA3xx processors (NFCv1)
189 - 32-bit Armada platforms (XP, 37x, 38x, 39x) (NFCv2)
190 - 64-bit Aramda platforms (7k, 8k) (NFCv2)
236 originally designed for Set-Top Box but is used on various BCM7xxx,
277 Controller Module with built-in hardware ECC capabilities.
[all …]
/Linux-v5.10/arch/mips/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
124 bool "Generic board-agnostic MIPS kernel"
178 bool "Alchemy processor based machines"
211 Support for the Texas Instruments AR7 System-on-a-Chip
282 Build a generic DT-based kernel image that boots on select
283 BCM33xx cable modem chips, BCM63xx DSL chips, and BCM7xxx set-top
373 see the Linux/MIPS FAQ on <http://www.linux-mips.org/> and the
374 DECstation porting pages on <http://decstation.unix-ag.org/>.
413 Olivetti M700-10 workstations.
447 bool "Loongson 32-bit family of machines"
[all …]
/Linux-v5.10/arch/arm/
DKconfig1 # SPDX-License-Identifier: GPL-2.0
129 The ARM series is a line of low-power-consumption RISC chip designs
131 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
132 manufactured, but legacy ARM-based PC hardware remains popular in
242 Patch phys-to-virt and virt-to-phys translation functions at
246 This can only be used with non-XIP MMU kernels where the base
292 bool "MMU-based Paged Memory Management Support"
295 Select if you want MMU-based virtualised addressing space
334 bool "ARMv7-M based platforms (Cortex-M0/M3/M4)"
347 bool "EBSA-110"
[all …]
/Linux-v5.10/lib/
DKconfig.debug1 # SPDX-License-Identifier: GPL-2.0-only
19 parameter printk.time=1. See Documentation/admin-guide/kernel-parameters.rst
26 in task context) or a caller "processor id" (if not in task context)
39 int "Default console loglevel (1-15)"
49 Note: This does not affect the log level of un-prefixed printk()
54 int "quiet console loglevel (1-15)"
65 int "Default message log level (1-7)"
71 This was hard-coded to KERN_WARNING since at least 2.6.10 but folks
107 enabled/disabled based on various levels of scope - per source file,
147 nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >
[all …]
/Linux-v5.10/Documentation/admin-guide/
Dkernel-parameters.txt5 force -- enable ACPI if default was off
6 on -- enable ACPI but allow fallback to DT [arm64]
7 off -- disable ACPI if default was on
8 noirq -- do not use ACPI for IRQ routing
9 strict -- Be less tolerant of platforms that are not
11 rsdt -- prefer RSDT over (default) XSDT
12 copy_dsdt -- copy DSDT to memory
26 If set to vendor, prefer vendor-specific driver
58 Documentation/firmware-guide/acpi/debug.rst for more information about
61 Enable processor driver info messages:
[all …]
/Linux-v5.10/mm/
Dvmscan.c1 // SPDX-License-Identifier: GPL-2.0
34 #include <linux/backing-dev.h>
158 if ((_page)->lru.prev != _base) { \
161 prev = lru_to_page(&(_page->lru)); \
162 prefetchw(&prev->_field); \
178 WARN_ON_ONCE(rs && task->reclaim_state); in set_task_reclaim_state()
180 /* Check for the nulling of an already-nulled member */ in set_task_reclaim_state()
181 WARN_ON_ONCE(!rs && !task->reclaim_state); in set_task_reclaim_state()
183 task->reclaim_state = rs; in set_task_reclaim_state()
191 * We allow subsystems to populate their shrinker-related
[all …]
/Linux-v5.10/kernel/sched/
Dfair.c1 // SPDX-License-Identifier: GPL-2.0
26 * Targeted preemption latency for CPU-bound tasks:
29 * 'timeslice length' - timeslices in CFS are of variable length
30 * and have no persistent notion like in traditional, time-slice
34 * run vmstat and monitor the context-switches (cs) field)
42 * The initial- and re-scaling of tunables is configurable
46 * SCHED_TUNABLESCALING_NONE - unscaled, always *1
47 * SCHED_TUNABLESCALING_LOG - scaled logarithmical, *1+ilog(ncpus)
48 * SCHED_TUNABLESCALING_LINEAR - scaled linear, *ncpus
55 * Minimal preemption granularity for CPU-bound tasks:
[all …]