Home
last modified time | relevance | path

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

12345678910>>...22

/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-class-remoteproc4 Description: Remote processor firmware
7 remote processor.
9 To change the running firmware, ensure the remote processor is
15 Description: Remote processor state
17 Reports the state of the remote processor, which will be one of:
25 "offline" means the remote processor is powered off.
27 "suspended" means that the remote processor is suspended and
30 "running" is the normal state of an available remote processor
33 the remote processor.
35 "invalid" is returned if the remote processor is in an
[all …]
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-v5.10/arch/arm/include/asm/
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-v5.10/Documentation/devicetree/bindings/soc/qcom/
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
43 Each processor's state bits are described by a subnode of the smsm device node.
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
[all …]
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-v5.10/arch/arm/mach-imx/
DKconfig59 This enables support for Freescale i.MX31 processor
66 This enables support for Freescale i.MX31 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.
166 This enables support for Freescale i.MX6 SoloLite processor.
[all …]
/Linux-v5.10/drivers/cpufreq/
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-v5.10/arch/sh/
DKconfig77 The SuperH is a RISC processor targeted for use in embedded systems
225 bool "Support SH7619 processor"
230 bool "Support J2 processor"
238 bool "Support SH7201 processor"
244 bool "Support SH7203 processor"
252 bool "Support SH7206 processor"
258 bool "Support SH7263 processor"
265 bool "Support SH7264 processor"
273 bool "Support SH7269 processor"
281 bool "Support MX-G processor"
[all …]
/Linux-v5.10/arch/m68k/
DKconfig.cpu10 the full 68000 processor instruction set.
12 of the 68000 processor family. They are mainly targeted at embedded
15 processor instruction set.
17 MC68xxx processor, select M68KCLASSIC.
19 processor, select COLDFIRE.
60 based on the 68020 processor. For the most part it is used in
70 processor, say Y. Otherwise, say N. Note that the 68020 requires a
81 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
91 or MC68040 processor, say Y. Otherwise, say N. Note that an
102 processor, say Y. Otherwise, say N.
[all …]
/Linux-v5.10/Documentation/admin-guide/acpi/
Dcppc_sysfs.rst11 performance of a logical processor on a contigious 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-v5.10/Documentation/admin-guide/pm/
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
26 ``intel_idle`` uses the ``MWAIT`` instruction to inform the processor that the
28 processor's functional blocks into low-power states. That instruction takes two
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
58 for different processor models included in the driver itself and the ACPI tables
59 of the system. The former are always used if the processor model at hand is
[all …]
/Linux-v5.10/Documentation/core-api/
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
33 data specific to the currently executing processor. Only the current
34 processor should be accessing that variable and therefore there are no
71 the processor. So the relocation to the per cpu base is encoded in the
88 prevent the kernel from moving the thread to a different processor
111 reserved for a specific processor. Without disabling preemption in the
116 the value of the individual counters for each processor are
[all …]
/Linux-v5.10/arch/x86/kernel/acpi/
Dboot.c186 struct acpi_madt_local_x2apic *processor = NULL; in acpi_parse_x2apic() local
192 processor = (struct acpi_madt_local_x2apic *)header; in acpi_parse_x2apic()
194 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_x2apic()
200 apic_id = processor->local_apic_id; in acpi_parse_x2apic()
201 enabled = processor->lapic_flags & ACPI_MADT_ENABLED; in acpi_parse_x2apic()
220 acpi_register_lapic(apic_id, processor->uid, enabled); in acpi_parse_x2apic()
231 struct acpi_madt_local_apic *processor = NULL; in acpi_parse_lapic() local
233 processor = (struct acpi_madt_local_apic *)header; in acpi_parse_lapic()
235 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_lapic()
241 if (processor->id == 0xff) in acpi_parse_lapic()
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/remoteproc/
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
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.
Dwkup_m3_rproc.txt4 The TI AM33xx and AM43xx family of devices use a small Cortex M3 co-processor
6 that cannot be controlled from the MPU. This CM3 processor requires a firmware
12 A wkup_m3 device node is used to represent the Wakeup M3 processor instance
29 booting the wkup_m3 remote processor.
/Linux-v5.10/Documentation/staging/
Dremoteproc.rst8 Modern SoCs typically have heterogeneous remote processor devices in asymmetric
29 existing virtio drivers with remote processor backends at a minimal development
39 Boot a remote processor (i.e. load its firmware, power it on, ...).
41 If the remote processor is already powered on, this function immediately
54 Power off a remote processor (previously booted with rproc_boot()).
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,
[all …]
Drpmsg.rst14 Modern SoCs typically employ heterogeneous remote processor devices in
26 multimedia tasks from the main application processor.
34 hardware accessible only by the remote processor, reserving kernel-controlled
35 resources on behalf of the remote processor, etc..).
48 to the processor. To minimize the risks of rogue (or buggy) userland code
54 Every rpmsg device is a communication channel with a remote processor (thus
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
[all …]
/Linux-v5.10/drivers/acpi/
DMakefile78 obj-$(CONFIG_ACPI_PROCESSOR) += processor.o
98 processor-y := processor_driver.o
99 processor-$(CONFIG_ACPI_PROCESSOR_IDLE) += processor_idle.o
100 processor-$(CONFIG_ACPI_CPU_FREQ_PSS) += processor_throttling.o \
102 processor-$(CONFIG_CPU_FREQ) += processor_perflib.o
/Linux-v5.10/drivers/hwmon/occ/
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-v5.10/Documentation/hwmon/
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-v5.10/drivers/remoteproc/
DKconfig31 on iMX7D) via the remote processor framework.
50 the remote processor framework.
62 and DSP on OMAP4) via the remote processor framework.
89 Say y here to support Wakeup M3 remote processor on TI AM33xx
103 remote processor framework.
123 via the remote processor framework.
244 processor framework.
257 remote processor framework.
271 Say m here to support TI's C66x and C71x DSP remote processor
273 processor framework.
[all …]
/Linux-v5.10/Documentation/devicetree/bindings/mailbox/
Domap-mailbox.txt6 various processor subsystems and is connected on an interconnect bus. The
12 within a processor subsystem, and there can be more than one line going to a
13 specific processor's interrupt controller. The interrupt line connections are
25 routed to different processor sub-systems on DRA7xx as they are routed through
29 all these clusters are multiplexed and routed to different processor subsystems
53 - ti,mbox-num-users: Number of targets (processor devices) that the mailbox
77 used for the communication between the host processor and a remote processor.
95 multiple interrupt lines connected to the MPU processor.
105 processor on AM33xx/AM43xx SoCs.
109 A device needing to communicate with a target processor device should specify
/Linux-v5.10/arch/arm64/kernel/
Dsmp.c548 acpi_map_gic_cpu_interface(struct acpi_madt_generic_interrupt *processor) in acpi_map_gic_cpu_interface() argument
550 u64 hwid = processor->arm_mpidr; in acpi_map_gic_cpu_interface()
552 if (!(processor->flags & ACPI_MADT_ENABLED)) { in acpi_map_gic_cpu_interface()
575 cpu_madt_gicc[0] = *processor; in acpi_map_gic_cpu_interface()
585 cpu_madt_gicc[cpu_count] = *processor; in acpi_map_gic_cpu_interface()
596 acpi_set_mailbox_entry(cpu_count, processor); in acpi_map_gic_cpu_interface()
605 struct acpi_madt_generic_interrupt *processor; in acpi_parse_gic_cpu_interface() local
607 processor = (struct acpi_madt_generic_interrupt *)header; in acpi_parse_gic_cpu_interface()
608 if (BAD_MADT_GICC_ENTRY(processor, end)) in acpi_parse_gic_cpu_interface()
613 acpi_map_gic_cpu_interface(processor); in acpi_parse_gic_cpu_interface()
/Linux-v5.10/Documentation/admin-guide/hw-vuln/
Dspecial-register-buffer-data-sampling.rst21 A processor is affected by SRBDS if its Family_Model and stepping is
66 processor.
101 Setting IA32_MCU_OPT_CTRL[0] (RNGDS_MITG_DIS) to 1 for a logical processor
103 enclave on that logical processor. Opting out of the mitigation for a
104 particular logical processor does not affect the RDRAND and RDSEED mitigations
139 hypervisor status Running on virtual guest processor that is
141 processor is mitigated or vulnerable.
146 This new microcode serializes processor access during execution of RDRAND,

12345678910>>...22