| /openbmc/linux/Documentation/ABI/testing/ |
| H A 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 …]
|
| H A 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
|
| /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/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.
154 This enables support for Freescale i.MX6 SoloLite processor.
[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/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
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 …]
|
| /openbmc/linux/arch/sh/ |
| H A D | Kconfig | 78 The SuperH is a RISC processor targeted for use in embedded systems
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"
[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/openbmc/meta-openembedded/meta-oe/recipes-multimedia/libopus/ |
| H A D | libopus_1.5.2.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/arch/m68k/ |
| H A 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.
63 processor, say Y. Otherwise, say N. Note that the 68020 requires a
74 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
84 or MC68040 processor, say Y. Otherwise, say N. Note that an
95 processor, say Y. Otherwise, say N.
102 Motorola 68328 processor support.
[all …]
|
| /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/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
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 …]
|
| /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/linux/drivers/remoteproc/ |
| H A 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 …]
|
| /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/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
33 data specific to the currently executing processor. Only the current
34 processor should be accessing that variable and therefore there are no
70 the processor. So the relocation to the per cpu base is encoded in the
87 prevent the kernel from moving the thread to a different processor
110 reserved for a specific processor. Without disabling preemption in the
115 the value of the individual counters for each processor are
[all …]
|
| /openbmc/linux/arch/x86/kernel/acpi/ |
| H A D | boot.c | 210 struct acpi_madt_local_x2apic *processor = NULL; in acpi_parse_x2apic() local
216 processor = (struct acpi_madt_local_x2apic *)header; in acpi_parse_x2apic()
218 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_x2apic()
224 apic_id = processor->local_apic_id; in acpi_parse_x2apic()
225 enabled = processor->lapic_flags & ACPI_MADT_ENABLED; in acpi_parse_x2apic()
232 if (!acpi_is_processor_usable(processor->lapic_flags)) in acpi_parse_x2apic()
248 acpi_register_lapic(apic_id, processor->uid, enabled); in acpi_parse_x2apic()
259 struct acpi_madt_local_apic *processor = NULL; in acpi_parse_lapic() local
261 processor = (struct acpi_madt_local_apic *)header; in acpi_parse_lapic()
263 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_lapic()
[all …]
|
| /openbmc/linux/Documentation/staging/ |
| H A 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 …]
|
| H A 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 …]
|
| /openbmc/linux/drivers/hwmon/occ/ |
| H A D | Kconfig | 12 On-Chip Controller (OCC) on a POWER8 processor. However, this driver
14 the P8, not the POWER processor itself. Communications with the OCC are
26 On-Chip Controller (OCC) on a POWER9 processor. However, this driver
28 the P9, not the POWER processor itself. Communications with the OCC are
|
| /openbmc/linux/Documentation/devicetree/bindings/remoteproc/ |
| H A 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
|
| /openbmc/openbmc/meta-arm/meta-arm-bsp/recipes-kernel/linux/files/corstone1000/ |
| H A D | 0001-remoteproc-Add-Arm-remoteproc-driver.patch | 10 switch on or off the remote processor.
61 + processor framework.
111 + * struct arm_rproc_reset_cfg - remote processor reset configuration
123 + * struct arm_rproc_dcfg - Arm remote processor configuration
133 + * struct arm_rproc - Arm remote processor instance
163 + * @rproc: pointer to the remote processor object
187 + * @rproc: pointer to the remote processor object
237 + * @rproc: pointer to the remote processor object
290 + * @rproc: pointer to the remote processor object
307 + * @rproc: pointer to the remote processor objec
[all...] |