| /linux-6.1.9/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-6.1.9/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-6.1.9/arch/arm/mach-imx/ |
| D | Kconfig | 47 This enables support for Freescale i.MX31 processor
54 This enables support for Freescale i.MX35 processor
66 This enables support for Freescale i.MX1 processor
78 This enables support for Freescale i.MX25 processor
86 This enables support for Freescale i.MX27 processor
105 This enables support for Freescale i.MX50 processor.
112 This enables support for Freescale i.MX51 processor
120 This enables support for Freescale i.MX53 processor.
144 This enables support for Freescale i.MX6 Quad processor.
154 This enables support for Freescale i.MX6 SoloLite processor.
[all …]
|
| /linux-6.1.9/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smsm.yaml | 16 information between the processors in a Qualcomm SoC. Each processor is
17 assigned 32 bits of state that can be modified. A processor can through a
19 certain bit owned by a certain remote processor.
32 Identifier of the local processor in the list of hosts, or in other words
34 processor.
49 remote processor.
54 Each processor's state bits are described by a subnode of the SMSM device
56 remote processor's state bits or the local processors bits. The node
66 belong to a remote processor.
74 One entry specifying remote IRQ used by the remote processor to
[all …]
|
| /linux-6.1.9/Documentation/powerpc/ |
| D | elf_hwcaps.rst | 80 The processor is PowerPC 601.
93 The processor is 40x or 44x family.
96 The processor has a unified L1 cache for instructions and data, as
98 Unused in the kernel since 39c8bf2b3cc1 ("powerpc: Retire e200 core (mpc555x processor)")
111 This is a 601 specific HWCAP, so if it is known that the processor
117 The processor is POWER4 or PPC970/FX/MP.
121 The processor is POWER5.
124 The processor is POWER5+.
127 The processor is Cell.
130 The processor implements the embedded category ("BookE") architecture.
[all …]
|
| /linux-6.1.9/Documentation/devicetree/bindings/interrupt-controller/ |
| D | fsl,mu-msi.yaml | 16 for one processor (A side) to signal the other processor (B side) using
45 - const: processor-a-side
46 - const: processor-b-side
62 - const: processor-a-side
63 - const: processor-b-side
94 reg-names = "processor-a-side", "processor-b-side";
98 power-domain-names = "processor-a-side", "processor-b-side";
|
| /linux-6.1.9/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()
|
| /linux-6.1.9/Documentation/devicetree/bindings/remoteproc/ |
| D | ti,omap-remoteproc.yaml | 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
21 The OMAP SoCs usually have a DSP processor sub-system and/or an IPU processor
22 sub-system. The DSP processor sub-system can contain any of the TI's C64x,
23 C66x or C67x family of DSP cores as the main execution unit. The IPU processor
27 Each remote processor sub-system is represented as a single DT node. Each node
29 the host processor (MPU) to perform the device management of the remote
30 processor and to communicate with the remote processor. The various properties
54 for this remote processor to access any external RAM memory or
[all …]
|
| D | renesas,rcar-rproc.yaml | 7 title: Renesas R-Car remote processor controller bindings
15 R-Car gen3 family may have a realtime processor, this processor shares peripheral
16 and RAM with the host processor with the same address map.
32 the remote processor (e.g. remoteproc firmware and carveouts, rpmsg
|
| 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 | ti,k3-dsp-rproc.yaml | 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
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.
56 communication with the remote processor. This property should match
|
| 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.
|
| /linux-6.1.9/arch/sh/ |
| D | Kconfig | 72 The SuperH is a RISC processor targeted for use in embedded systems
217 bool "Support SH7619 processor"
222 bool "Support J2 processor"
230 bool "Support SH7201 processor"
236 bool "Support SH7203 processor"
244 bool "Support SH7206 processor"
250 bool "Support SH7263 processor"
257 bool "Support SH7264 processor"
265 bool "Support SH7269 processor"
273 bool "Support MX-G processor"
[all …]
|
| /linux-6.1.9/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.
64 processor, say Y. Otherwise, say N. Note that the 68020 requires a
75 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
85 or MC68040 processor, say Y. Otherwise, say N. Note that an
96 processor, say Y. Otherwise, say N.
103 Motorola 68328 processor support.
[all …]
|
| /linux-6.1.9/Documentation/admin-guide/acpi/ |
| D | cppc_sysfs.rst | 13 performance of a logical processor on a contiguous and abstract performance
40 * highest_perf : Highest performance of this processor (abstract scale).
41 * nominal_perf : Highest sustained performance of this processor
43 * lowest_nonlinear_perf : Lowest performance of this processor with nonlinear
45 * lowest_perf : Lowest performance of this processor (abstract scale).
49 The above frequencies should only be used to report processor performance in
54 Reference counter ticks up proportional to processor's reference performance.
55 Delivered counter ticks up proportional to processor's delivered performance.
|
| /linux-6.1.9/Documentation/admin-guide/pm/ |
| D | intel_idle.rst | 20 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
59 for different processor models included in the driver itself and the ACPI tables
60 of the system. The former are always used if the processor model at hand is
[all …]
|
| /linux-6.1.9/Documentation/peci/ |
| D | peci.rst | 8 interface between Intel processor and management controllers
13 controller is acting as a PECI originator and the processor - as
15 PECI can be used in both single processor and multiple-processor based
35 For PECI Wire, each processor package will utilize unique, fixed
37 have a fixed relationship with the processor socket ID - if one of the
|
| /linux-6.1.9/drivers/remoteproc/ |
| D | Kconfig | 33 processor framework.
44 processor framework.
63 the remote processor framework.
75 and DSP on OMAP4) via the remote processor framework.
102 Say y here to support Wakeup M3 remote processor on TI AM33xx
116 remote processor framework.
136 via the remote processor framework.
142 tristate "Amlogic Meson6/8/8b/8m2 AO ARC remote processor support"
147 Say m or y here to have support for the AO ARC remote processor
158 subsystem via the remote processor framework.
[all …]
|
| /linux-6.1.9/Documentation/core-api/ |
| D | this_cpu_ops.rst | 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 …]
|
| /linux-6.1.9/arch/x86/kernel/acpi/ |
| D | boot.c | 194 struct acpi_madt_local_x2apic *processor = NULL; in acpi_parse_x2apic() local
200 processor = (struct acpi_madt_local_x2apic *)header; in acpi_parse_x2apic()
202 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_x2apic()
208 apic_id = processor->local_apic_id; in acpi_parse_x2apic()
209 enabled = processor->lapic_flags & ACPI_MADT_ENABLED; in acpi_parse_x2apic()
228 acpi_register_lapic(apic_id, processor->uid, enabled); in acpi_parse_x2apic()
239 struct acpi_madt_local_apic *processor = NULL; in acpi_parse_lapic() local
241 processor = (struct acpi_madt_local_apic *)header; in acpi_parse_lapic()
243 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_lapic()
249 if (processor->id == 0xff) in acpi_parse_lapic()
[all …]
|
| /linux-6.1.9/Documentation/staging/ |
| D | remoteproc.rst | 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()).
76 the remote processor's refcount, so always use rproc_put() to
91 /* let's power on and boot our remote processor */
100 * our remote processor is now powered on... give it some work
116 Allocate a new remote processor handle, but don't register
118 name of this remote processor, platform-specific ops handlers,
[all …]
|
| D | rpmsg.rst | 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-6.1.9/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-6.1.9/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
|