| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-class-remoteproc | 4 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 …]
|
| D | sysfs-bus-rpmsg | 7 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.4/arch/arm/include/asm/ |
| D | proc-fns.h | 23 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.4/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smsm.txt | 4 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 …]
|
| D | qcom,smd.txt | 15 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.4/drivers/cpufreq/ |
| D | speedstep-lib.c | 34 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()
|
| D | speedstep-lib.h | 36 extern unsigned int speedstep_get_frequency(enum speedstep_processor processor);
44 extern unsigned int speedstep_get_freqs(enum speedstep_processor processor,
|
| /Linux-v5.4/arch/m68k/ |
| D | Kconfig.cpu | 10 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.4/arch/sh/ |
| D | Kconfig | 59 The SuperH is a RISC processor targeted for use in embedded systems
248 bool "Support SH7619 processor"
253 bool "Support J2 processor"
261 bool "Support SH7201 processor"
267 bool "Support SH7203 processor"
275 bool "Support SH7206 processor"
281 bool "Support SH7263 processor"
288 bool "Support SH7264 processor"
296 bool "Support SH7269 processor"
304 bool "Support MX-G processor"
[all …]
|
| /Linux-v5.4/Documentation/admin-guide/acpi/ |
| D | cppc_sysfs.rst | 11 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.4/Documentation/ |
| D | this_cpu_ops.txt | 9 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 …]
|
| D | remoteproc.txt | 8 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 …]
|
| D | rpmsg.txt | 14 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.4/arch/x86/kernel/acpi/ |
| D | boot.c | 185 struct acpi_madt_local_x2apic *processor = NULL; in acpi_parse_x2apic() local
191 processor = (struct acpi_madt_local_x2apic *)header; in acpi_parse_x2apic()
193 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_x2apic()
199 apic_id = processor->local_apic_id; in acpi_parse_x2apic()
200 enabled = processor->lapic_flags & ACPI_MADT_ENABLED; in acpi_parse_x2apic()
219 acpi_register_lapic(apic_id, processor->uid, enabled); in acpi_parse_x2apic()
230 struct acpi_madt_local_apic *processor = NULL; in acpi_parse_lapic() local
232 processor = (struct acpi_madt_local_apic *)header; in acpi_parse_lapic()
234 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_lapic()
240 if (processor->id == 0xff) in acpi_parse_lapic()
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/remoteproc/ |
| D | st-rproc.txt | 7 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
|
| D | stm32-rproc.txt | 9 remote processor.
10 - resets: Reference to a reset controller asserting the remote processor.
12 remote processor reset hold boot
43 memories shared with the remote processor (eg: remoteproc
47 processor deep sleep setting
52 firmware and starts the remote processor.
|
| D | ti,keystone-rproc.txt | 5 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.
|
| D | wkup_m3_rproc.txt | 4 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.4/drivers/hwmon/occ/ |
| D | Kconfig | 13 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.4/Documentation/hwmon/ |
| D | fam15h_power.rst | 28 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.4/drivers/acpi/ |
| D | Makefile | 79 obj-$(CONFIG_ACPI_PROCESSOR) += processor.o
99 processor-y := processor_driver.o
100 processor-$(CONFIG_ACPI_PROCESSOR_IDLE) += processor_idle.o
101 processor-$(CONFIG_ACPI_CPU_FREQ_PSS) += processor_throttling.o \
103 processor-$(CONFIG_CPU_FREQ) += processor_perflib.o
|
| /Linux-v5.4/arch/arm64/kernel/ |
| D | smp.c | 517 acpi_map_gic_cpu_interface(struct acpi_madt_generic_interrupt *processor) in acpi_map_gic_cpu_interface() argument
519 u64 hwid = processor->arm_mpidr; in acpi_map_gic_cpu_interface()
521 if (!(processor->flags & ACPI_MADT_ENABLED)) { in acpi_map_gic_cpu_interface()
544 cpu_madt_gicc[0] = *processor; in acpi_map_gic_cpu_interface()
554 cpu_madt_gicc[cpu_count] = *processor; in acpi_map_gic_cpu_interface()
565 acpi_set_mailbox_entry(cpu_count, processor); in acpi_map_gic_cpu_interface()
574 struct acpi_madt_generic_interrupt *processor; in acpi_parse_gic_cpu_interface() local
576 processor = (struct acpi_madt_generic_interrupt *)header; in acpi_parse_gic_cpu_interface()
577 if (BAD_MADT_GICC_ENTRY(processor, end)) in acpi_parse_gic_cpu_interface()
582 acpi_map_gic_cpu_interface(processor); in acpi_parse_gic_cpu_interface()
|
| /Linux-v5.4/Documentation/devicetree/bindings/mailbox/ |
| D | omap-mailbox.txt | 6 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.4/Documentation/powerpc/ |
| D | vcpudispatch_stats.txt | 5 static mapping of the LPAR processors (vcpus) to physical processor
7 on their associated physical processor chip. However, under certain
8 scenarios, vcpus may be dispatched on a different processor chip (away
26 2. number of times this vcpu was dispatched on the same processor as last
28 3. number of times this vcpu was dispatched on a different processor core
|
| /Linux-v5.4/Documentation/admin-guide/pm/ |
| D | intel_pstate.rst | 60 on the capabilities of the processor.
86 enabled in the processor and possibly on the processor model.
96 If the processor supports the HWP feature, it will be enabled during the
97 processor initialization and cannot be disabled after that. It is possible
101 If the HWP feature has been enabled, ``intel_pstate`` relies on the processor to
102 select P-states by itself, but still it can give hints to the processor's
107 Even though the P-state selection is carried out by the processor automatically,
116 In this configuration ``intel_pstate`` will write 0 to the processor's
118 Energy-Performance Bias (EPB) knob (otherwise), which means that the processor's
124 Also, in this configuration the range of P-states available to the processor's
[all …]
|
