| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-remoteproc | 4 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 …]
|
| /openbmc/linux/arch/arm/include/asm/ |
| H A 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()
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | Cpu.interface.yaml | 12 A free form string indicates processor family type. For example,
13 values can be "Intel Xeon processor", "AS400 Family", etc.
19 this processor in unsigned integer. Default set to 0x02 which is
26 this processor in unsigned integer.
31 This Processor ID field contains processor-specific information that
32 describes the processor's features. Details depend on processor
43 The set of boolean flags for processor's capability, such as 64-bit
49 The number of cores in the processor.
53 The maximum number of threads the processor can support.
57 The step value for this processor
[all …]
|
| /openbmc/linux/arch/arm/mach-imx/ |
| H A 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.
191 This enables support for Freescale LS1021A processor.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/qcom/ |
| H A 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.
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
115 # the wireless processor, defined from the 8974 apps processor's
[all …]
|
| /openbmc/smbios-mdr/include/ |
| H A D | cpu.hpp | 43 using processor = sdbusplus::server::xyz::openbmc_project::inventory::item::Cpu; typedef
291 static const std::array<std::optional<processor::Capability>, 16>
295 processor::Capability::Capable64bit,
296 processor::Capability::MultiCore,
297 processor::Capability::HardwareThread,
298 processor::Capability::ExecuteProtection,
299 processor::Capability::EnhancedVirtualization,
300 processor::Capability::PowerPerformanceControl,
311 sdbusplus::server::object_t<processor, asset, location, connector, rev,
324 sdbusplus::server::object_t<processor, asset, location, connector, rev, in Cpu()
|
| /openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
| H A 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";
|
| /openbmc/linux/Documentation/powerpc/ |
| H A 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
117 The processor is POWER4 or PPC970/FX/MP.
121 The processor is POWER5.
124 The processor is POWER5+.
127 The processor is Cell.
133 The processor implements SMT.
150 The processor is PA6T.
156 The processor is POWER6.
[all …]
|
| /openbmc/linux/drivers/cpufreq/ |
| H A 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()
|
| /openbmc/linux/arch/sh/ |
| H A D | Kconfig | 223 bool "Support SH7619 processor"
228 bool "Support J2 processor"
236 bool "Support SH7201 processor"
242 bool "Support SH7203 processor"
250 bool "Support SH7206 processor"
256 bool "Support SH7263 processor"
263 bool "Support SH7264 processor"
271 bool "Support SH7269 processor"
279 bool "Support MX-G processor"
288 bool "Support SH7705 processor"
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-multimedia/libopus/ |
| H A D | libopus_1.5.1.bb | 42 #| {standard input}:389: Error: selected processor does not support Thumb mode `smull r5,r7,r1,r4'
43 #| {standard input}:418: Error: selected processor does not support Thumb mode `smull r5,r6,r4,r1'
44 #| {standard input}:448: Error: selected processor does not support Thumb mode `smull r4,r5,r1,r0'
45 #| {standard input}:474: Error: selected processor does not support Thumb mode `smull r0,r4,r8,r1'
46 #| {standard input}:510: Error: selected processor does not support Thumb mode `smull fp,r0,r10,r1'
47 #| {standard input}:553: Error: selected processor does not support Thumb mode `smull fp,r1,r10,r3'
48 #| {standard input}:741: Error: selected processor does not support Thumb mode `smull r3,r0,r6,r10'
49 #| {standard input}:761: Error: selected processor does not support Thumb mode `smull fp,r2,r3,r9'
50 #| {standard input}:773: Error: selected processor does not support Thumb mode `smull fp,r3,r5,r8'
|
| /openbmc/smbios-mdr/src/ |
| H A D | cpu.cpp | 32 processor::socket(result); in socket()
44 processor::family("Unknown Processor Family"); in family()
52 processor::family("Unknown Processor Family"); in family()
56 processor::family(it2->second); in family()
57 processor::effectiveFamily(family2); in family()
62 processor::family(it->second); in family()
63 processor::effectiveFamily(family); in family()
103 std::vector<processor::Capability> result; in characteristics()
104 std::optional<processor::Capability> cap; in characteristics()
118 processor::characteristics(result); in characteristics()
|
| /openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
| H A D | ti,omap-remoteproc.yaml | 21 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
150 processor sub-system is running in SMP mode, or one per
151 core in the processor sub-system. This can also be used
166 serve as Watchdog timers for the processor cores. This
167 will usually be one per executing processor core, even
[all …]
|
| H A D | xlnx,zynqmp-r5fss.yaml | 7 title: Xilinx R5F processor subsystem
15 real-time processing based on the Cortex-R5F processor core from ARM.
16 The Cortex-R5F processor implements the Arm v7-R architecture and includes a
27 The RPU MPCore can operate in split mode (Dual-processor performance), Safety
30 core 1 runs normally). The processor does not support dynamic configuration.
31 Switching between modes is only permitted immediately after a processor reset.
44 Each processor includes separate L1 instruction and data caches and
50 per processor. In lock-step mode, the processor has access to 256KB of
91 the remote processor (e.g. remoteproc firmware and carveouts, rpmsg
|
| H A D | renesas,rcar-rproc.yaml | 7 title: Renesas R-Car remote processor controller
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
|
| /openbmc/linux/Documentation/admin-guide/acpi/ |
| H A 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.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/meta-python/recipes-dbs/mongodb/mongodb/ |
| H A D | arm64-support.patch | 32 @@ -309,7 +309,7 @@ if processor == 'i386' or processor == 'emscripten':
33 elif processor == 'arm':
36 -elif processor == "aarch64":
37 +elif processor == "aarch64" or processor == 'arm64':
|
| /openbmc/linux/arch/m68k/ |
| H A D | Kconfig.cpu | 10 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.
102 Motorola 68328 processor support.
109 Motorola 68EX328 processor support.
116 Motorola 68VZ328 processor support.
137 Motorola ColdFire 5206 processor support.
174 Motorola ColdFire 5249 processor support.
[all …]
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A 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
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 …]
|
| /openbmc/linux/Documentation/peci/ |
| H A 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
|
| /openbmc/u-boot/doc/driver-model/ |
| H A D | remoteproc-framework.txt | 19 on various System on Chip(SoCs). The term remote processor is used to
20 indicate that this is not the processor on which U-Boot is operating
22 the processor on which we are functional.
68 NOTE: It depends on the remote processor as to the exact behavior
72 allow us to start the processor(image from a EEPROM/OTP) etc.
79 Remote processor can operate on a certain firmware that maybe loaded
92 {.compatible = "sandbox,test-processor"},
154 compatible = "sandbox,test-processor";
159 compatible = "sandbox,test-processor";
|
| /openbmc/linux/arch/loongarch/kernel/ |
| H A D | acpi.c | 94 struct acpi_madt_core_pic *processor = NULL; in acpi_parse_processor() local
96 processor = (struct acpi_madt_core_pic *)header; in acpi_parse_processor()
97 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_processor()
102 acpi_core_pic[processor->core_id] = *processor; in acpi_parse_processor()
103 set_processor_mask(processor->core_id, processor->flags); in acpi_parse_processor()
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/Cpu/ |
| H A D | OperatingConfig.interface.yaml | 3 (but not necessarily active/applied) processor configuration profile.
7 description: The base clock speed of the processor in MHz.
27 The maximum clock speed to which the processor can be configured in
33 description: The thermal design point of the processor in watts.
39 The number of cores in the processor that can be used in this
|
| /openbmc/linux/drivers/remoteproc/ |
| H A D | Kconfig | 33 processor framework.
44 processor framework.
63 the remote processor framework.
116 remote processor framework.
136 via the remote processor framework.
158 subsystem via the remote processor framework.
308 processor framework.
321 remote processor framework.
337 processor framework.
353 a slave processor.
[all …]
|
| /openbmc/linux/Documentation/core-api/ |
| H A 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
115 the value of the individual counters for each processor are
121 the same code paths. Since each processor has its own per cpu
136 processor. this_cpu_ptr avoids multiple steps that the common
137 get_cpu/put_cpu sequence requires. No processor number is
145 no longer point to per cpu data of the current processor.
327 remotely from one processor and the local processor would use this_cpu ops
[all …]
|