Home
last modified time | relevance | path

Searched refs:processor (Results 1 – 25 of 3353) sorted by relevance

12345678910>>...135

/linux/Documentation/ABI/testing/
A Dsysfs-class-remoteproc4 Description: Remote processor firmware
7 remote processor.
15 Description: Remote processor state
25 "offline" means the remote processor is powered off.
33 the remote processor.
35 "invalid" is returned if the remote processor is in an
56 Description: Remote processor name
65 Description: Remote processor coredump configuration
80 "inline" means when the remote processor's coredump is
89 Description: Remote processor recovery mechanism
[all …]
A Dsysfs-bus-rpmsg7 processor. Channels are identified with a (textual) name,
19 processor. Channels have a local ("source") rpmsg address,
37 processor. Channels have a local ("source") rpmsg address,
48 remote processor. This make it a local rpmsg server,
59 processor. Channels are identified by a textual name (see
69 to the other processor, in order to let it know about the
83 processor. Channels are identified by a textual name (see
89 remote processor is referred as rpmsg driver. The rpmsg device
/linux/arch/arm/include/asm/
A Dproc-fns.h23 struct processor { struct
82 static inline void init_proc_vtable(const struct processor *p) in init_proc_vtable() argument
103 extern struct processor processor;
113 extern struct processor *cpu_vtable[];
116 static inline void init_proc_vtable(const struct processor *p) in init_proc_vtable()
126 #define PROC_VTABLE(f) processor.f
127 #define PROC_TABLE(f) processor.f
128 static inline void init_proc_vtable(const struct processor *p) in init_proc_vtable()
130 processor = *p; in init_proc_vtable()
/linux/Documentation/devicetree/bindings/soc/qcom/
A Dqcom,smsm.txt4 information between the processors in a Qualcomm SoC. Each processor is
5 assigned 32 bits of state that can be modified. A processor can through a
7 certain bit owned by a certain remote processor.
19 signaling the N:th remote processor
27 Definition: identifier of the local processor in the list of hosts, or
29 matrix representing the local processor
45 processor's state bits or the local processors bits. The node names are not
63 to belong to a remote processor
73 Definition: one entry specifying remote IRQ used by the remote processor
79 wireless processor, defined from the 8974 apps processor's point-of-view. It
[all …]
A Dqcom,apr.yaml14 communication between Application processor and QDSP. APR/GPR is mainly
27 Selects the processor domain for apr
32 5 = Application processor Domain
42 Selects the processor domain for apr
47 5 = Application processor Domain
50 Selects the processor domain for gpr
91 11 = Core voice processor.
A Dqcom,smd.txt15 processor of some sort - or in SMD language an "edge". The name of the edges
22 Definition: should specify the IRQ used by the remote processor to
23 signal this processor about communication related updates
35 signaling the remote processor:
43 Definition: the identifier of the remote processor in the smd channel
49 Definition: the identifier for the remote processor as known by the rest
/linux/arch/arm/mach-imx/
A DKconfig59 This enables support for Freescale i.MX31 processor
66 This enables support for Freescale i.MX35 processor
78 This enables support for Freescale i.MX1 processor
90 This enables support for Freescale i.MX25 processor
98 This enables support for Freescale i.MX27 processor
117 This enables support for Freescale i.MX50 processor.
124 This enables support for Freescale i.MX51 processor
132 This enables support for Freescale i.MX53 processor.
156 This enables support for Freescale i.MX6 Quad processor.
203 This enables support for Freescale LS1021A processor.
[all …]
/linux/drivers/cpufreq/
A Dspeedstep-lib.c34 static unsigned int pentium3_get_frequency(enum speedstep_processor processor) in pentium3_get_frequency() argument
89 if (processor == SPEEDSTEP_CPU_PIII_C_EARLY) { in pentium3_get_frequency()
227 unsigned int speedstep_get_frequency(enum speedstep_processor processor) in speedstep_get_frequency() argument
229 switch (processor) { in speedstep_get_frequency()
240 return pentium3_get_frequency(processor); in speedstep_get_frequency()
381 unsigned int speedstep_get_freqs(enum speedstep_processor processor, in speedstep_get_freqs() argument
392 if ((!processor) || (!low_speed) || (!high_speed) || (!set_state)) in speedstep_get_freqs()
398 prev_speed = speedstep_get_frequency(processor); in speedstep_get_freqs()
409 *low_speed = speedstep_get_frequency(processor); in speedstep_get_freqs()
428 *high_speed = speedstep_get_frequency(processor); in speedstep_get_freqs()
/linux/Documentation/devicetree/bindings/remoteproc/
A Dti,omap-remoteproc.yaml21 The OMAP SoCs usually have a DSP processor sub-system and/or an IPU processor
30 processor and to communicate with the remote processor. The various properties
54 for this remote processor to access any external RAM memory or
58 sub-modules within the processor sub-system (eg: DRA7 DSPs),
75 Main functional clock for the remote processor
81 Reset handles for the remote processor
147 processor sub-system is running in SMP mode, or one per
148 core in the processor sub-system. This can also be used
161 serve as Watchdog timers for the processor cores. This
162 will usually be one per executing processor core, even
[all …]
A Dti,k3-dsp-rproc.yaml14 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
21 TMS320C71x CorePac processor.
25 host processor (Arm CorePac) to perform the device management of the remote
26 processor and to communicate with the remote processor.
54 communication with the remote processor. This property should match
A 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.
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.
56 the remote processor to the host processor. The values should
67 stack. This will be used to interrupt the remote processor.
A Dst-rproc.txt7 the bootloader starts a co-processor, the primary OS must detect its state
17 - clocks Clock for co-processor (See: ../clock/clock-bindings.txt)
18 - clock-frequency Clock frequency to set co-processor at if the bootloader
21 for the co-processor
/linux/arch/sh/
A DKconfig218 bool "Support SH7619 processor"
223 bool "Support J2 processor"
231 bool "Support SH7201 processor"
237 bool "Support SH7203 processor"
245 bool "Support SH7206 processor"
251 bool "Support SH7263 processor"
258 bool "Support SH7264 processor"
266 bool "Support SH7269 processor"
274 bool "Support MX-G processor"
283 bool "Support SH7705 processor"
[all …]
/linux/arch/m68k/
A DKconfig.cpu10 the full 68000 processor instruction set.
15 processor instruction set.
17 MC68xxx processor, select M68KCLASSIC.
19 processor, select COLDFIRE.
95 processor, say Y. Otherwise, say N.
103 Motorola 68328 processor support.
111 Motorola 68EX328 processor support.
119 Motorola 68VZ328 processor support.
140 Motorola ColdFire 5206 processor support.
177 Motorola ColdFire 5249 processor support.
[all …]
/linux/Documentation/admin-guide/pm/
A Dintel_idle.rst20 a particular processor model in it depends on whether or not it recognizes that
21 processor model and may also depend on information coming from the platform
30 first of which, referred to as a *hint*, can be used by the processor to
47 Each ``MWAIT`` hint value is interpreted by the processor as a license to
48 reconfigure itself in a certain way in order to save energy. The processor
52 processor) corresponding to them depends on the processor model and it may also
62 the given processor model (which is the case for all server processor models
63 recognized by ``intel_idle``) or if the processor model is not recognized.
65 tables with any processor model recognized by it; see
107 If the given processor model is not recognized by ``intel_idle``, but it
[all …]
/linux/Documentation/admin-guide/acpi/
A Dcppc_sysfs.rst11 performance of a logical processor on a contiguous and abstract performance
38 * highest_perf : Highest performance of this processor (abstract scale).
39 * nominal_perf : Highest sustained performance of this processor
41 * lowest_nonlinear_perf : Lowest performance of this processor with nonlinear
43 * lowest_perf : Lowest performance of this processor (abstract scale).
47 The above frequencies should only be used to report processor performance in
52 Reference counter ticks up proportional to processor's reference performance.
53 Delivered counter ticks up proportional to processor's delivered performance.
/linux/arch/x86/kernel/acpi/
A Dboot.c187 struct acpi_madt_local_x2apic *processor = NULL; in acpi_parse_x2apic() local
195 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_x2apic()
201 apic_id = processor->local_apic_id; in acpi_parse_x2apic()
232 struct acpi_madt_local_apic *processor = NULL; in acpi_parse_lapic() local
236 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_lapic()
242 if (processor->id == 0xff) in acpi_parse_lapic()
259 processor->processor_id, /* ACPI ID */ in acpi_parse_lapic()
268 struct acpi_madt_local_sapic *processor = NULL; in acpi_parse_sapic() local
272 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_sapic()
277 acpi_register_lapic((processor->id << 8) | processor->eid,/* APIC ID */ in acpi_parse_sapic()
[all …]
/linux/Documentation/core-api/
A Dthis_cpu_ops.rst9 variables associated with the *currently* executing processor. This is
12 specific processor).
14 this_cpu operations add a per cpu variable offset to the processor
21 processor is not changed between the calculation of the address and
116 the value of the individual counters for each processor are
122 the same code paths. Since each processor has its own per cpu
137 processor. this_cpu_ptr avoids multiple steps that the common
138 get_cpu/put_cpu sequence requires. No processor number is
146 no longer point to per cpu data of the current processor.
329 remotely from one processor and the local processor would use this_cpu ops
[all …]
/linux/Documentation/staging/
A Dremoteproc.rst39 Boot a remote processor (i.e. load its firmware, power it on, ...).
75 the remote processor's refcount, so always use rproc_put() to
90 /* let's power on and boot our remote processor */
99 * our remote processor is now powered on... give it some work
115 Allocate a new remote processor handle, but don't register
117 name of this remote processor, platform-specific ops handlers,
122 initialization of the remote processor.
126 the registration of the remote processor.
154 a new remote processor device is probed.
243 if the remote processor is accessing memory directly).
[all …]
A Drpmsg.rst14 Modern SoCs typically employ heterogeneous remote processor devices in
26 multimedia tasks from the main application processor.
35 resources on behalf of the remote processor, etc..).
73 sends a message across to the remote processor on a given channel.
80 one becomes available (i.e. until the remote processor consumes
92 sends a message across to the remote processor on a given channel,
98 The message will then be sent to the remote processor to which the
103 one becomes available (i.e. until the remote processor consumes
127 one becomes available (i.e. until the remote processor consumes
178 sends a message across to the remote processor, using source and
[all …]
/linux/drivers/remoteproc/
A DKconfig33 processor framework.
44 processor framework.
63 the remote processor framework.
75 and DSP on OMAP4) via the remote processor framework.
116 remote processor framework.
136 via the remote processor framework.
158 subsystem via the remote processor framework.
293 processor framework.
306 remote processor framework.
322 processor framework.
[all …]
/linux/Documentation/hwmon/
A Dfam15h_power.rst28 processor varies based on the workload being executed. Derated power
36 be calculated using different processor northbridge function
41 consumed by the processor for NB and logic external to the core.
45 the processor can support.
48 consumed by the processor.
57 attributes only for internal node0 of a multi-node processor.
62 calculate the average power consumed by a processor during a
/linux/arch/arm64/kernel/
A Dsmp.c523 acpi_map_gic_cpu_interface(struct acpi_madt_generic_interrupt *processor) in acpi_map_gic_cpu_interface() argument
525 u64 hwid = processor->arm_mpidr; in acpi_map_gic_cpu_interface()
527 if (!(processor->flags & ACPI_MADT_ENABLED)) { in acpi_map_gic_cpu_interface()
550 cpu_madt_gicc[0] = *processor; in acpi_map_gic_cpu_interface()
560 cpu_madt_gicc[cpu_count] = *processor; in acpi_map_gic_cpu_interface()
571 acpi_set_mailbox_entry(cpu_count, processor); in acpi_map_gic_cpu_interface()
580 struct acpi_madt_generic_interrupt *processor; in acpi_parse_gic_cpu_interface() local
582 processor = (struct acpi_madt_generic_interrupt *)header; in acpi_parse_gic_cpu_interface()
583 if (BAD_MADT_GICC_ENTRY(processor, end)) in acpi_parse_gic_cpu_interface()
588 acpi_map_gic_cpu_interface(processor); in acpi_parse_gic_cpu_interface()
/linux/drivers/hwmon/occ/
A DKconfig13 On-Chip Controller (OCC) on a POWER8 processor. However, this driver
15 the P8, not the POWER processor itself. Communications with the OCC are
28 On-Chip Controller (OCC) on a POWER9 processor. However, this driver
30 the P9, not the POWER processor itself. Communications with the OCC are
/linux/Documentation/devicetree/bindings/mailbox/
A Dti,omap-mailbox.yaml15 external to the various processor subsystems and is connected on an
21 controller within a processor subsystem, and there can be more than one line
22 going to a specific processor's interrupt controller. The interrupt line
35 lines can also be routed to different processor sub-systems on DRA7xx as they
40 to different processor subsystems over a limited number of common interrupt
54 A device needing to communicate with a target processor device should specify
91 receive messages between the host processor and a remote processor. Each
110 communicate with WkupM3 remote processor on AM33xx/AM43xx SoCs.
134 interrupts reaching the main processor. An interrupt-parent property
136 Interrupt Router before reaching the main processor's GIC.
[all …]

Completed in 42 milliseconds

12345678910>>...135