| /linux/Documentation/ABI/testing/ |
| 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 …]
|
| 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
|
| /linux/arch/arm/include/asm/ |
| 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()
|
| /linux/arch/arm/mach-imx/ |
| 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 …]
|
| /linux/Documentation/devicetree/bindings/soc/qcom/ |
| 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. 34 processor. 41 this client. Each entry represents the N:th remote processor by index 57 remote processor. 65 remote processor's state bits or the local processors bits. The node 75 belong to a remote processor. 83 One entry specifying remote IRQ used by the remote processor to 127 # the wireless processor, defined from the 8974 apps processor's [all …]
|
| /linux/Documentation/arch/powerpc/ |
| A D | elf_hwcaps.rst | 80 The processor is PowerPC 601. 93 The processor is 40x or 44x family. 97 The processor has a unified L1 cache for instructions and data, as 118 The processor is POWER4 or PPC970/FX/MP. 122 The processor is POWER5. 125 The processor is POWER5+. 128 The processor is Cell. 134 The processor implements SMT. 151 The processor is PA6T. 157 The processor is POWER6. [all …]
|
| /linux/arch/loongarch/kernel/ |
| A D | acpi.c | 104 struct acpi_madt_core_pic *processor = NULL; in acpi_parse_p1_processor() local 106 processor = (struct acpi_madt_core_pic *)header; in acpi_parse_p1_processor() 107 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_p1_processor() 112 acpi_core_pic[processor->core_id] = *processor; in acpi_parse_p1_processor() 113 if (processor->flags & ACPI_MADT_ENABLED) in acpi_parse_p1_processor() 114 set_processor_mask(processor->core_id, 1); in acpi_parse_p1_processor() 123 struct acpi_madt_core_pic *processor = NULL; in acpi_parse_p2_processor() local 125 processor = (struct acpi_madt_core_pic *)header; in acpi_parse_p2_processor() 126 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_p2_processor() 130 if (!(processor->flags & ACPI_MADT_ENABLED)) in acpi_parse_p2_processor() [all …]
|
| /linux/Documentation/devicetree/bindings/interrupt-controller/ |
| 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";
|
| /linux/drivers/cpufreq/ |
| 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()
|
| /linux/arch/sh/ |
| 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 …]
|
| /linux/Documentation/devicetree/bindings/remoteproc/ |
| 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 …]
|
| 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
|
| 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
|
| A 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/arch/m68k/ |
| A D | Kconfig.cpu | 10 the full 68000 processor instruction set. 15 processor instruction set. 17 MC68xxx processor, select M68KCLASSIC. 19 processor, select COLDFIRE. 97 processor, say Y. Otherwise, say N. 104 Motorola 68328 processor support. 111 Motorola 68EX328 processor support. 118 Motorola 68VZ328 processor support. 139 Motorola ColdFire 5206 processor support. 176 Motorola ColdFire 5249 processor support. [all …]
|
| /linux/Documentation/admin-guide/acpi/ |
| 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.
|
| /linux/drivers/remoteproc/ |
| A D | Kconfig | 33 processor framework. 44 processor framework. 63 the remote processor framework. 116 remote processor framework. 136 via the remote processor framework. 309 processor framework. 322 remote processor framework. 337 processor framework. 353 a remote processor. 365 a slave processor. [all …]
|
| /linux/Documentation/peci/ |
| 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
|
| /linux/Documentation/admin-guide/pm/ |
| 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 …]
|
| /linux/drivers/md/dm-vdo/indexer/ |
| A D | funnel-requestqueue.c | 53 uds_request_queue_processor_fn processor; member 144 queue->processor(request); in request_queue_worker() 191 queue->processor(request); in request_queue_worker() 195 uds_request_queue_processor_fn processor, in uds_make_request_queue() argument 205 queue->processor = processor; in uds_make_request_queue()
|
| /linux/arch/x86/kernel/acpi/ |
| A D | boot.c | 175 struct acpi_madt_local_x2apic *processor = NULL; in acpi_parse_x2apic() local 183 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_x2apic() 189 apic_id = processor->local_apic_id; in acpi_parse_x2apic() 232 struct acpi_madt_local_apic *processor = NULL; in acpi_parse_lapic() local 236 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_lapic() 242 if (processor->id == 0xff) in acpi_parse_lapic() 257 processor->processor_id, /* ACPI ID */ in acpi_parse_lapic() 267 struct acpi_madt_local_sapic *processor = NULL; in acpi_parse_sapic() local 271 if (BAD_MADT_ENTRY(processor, end)) in acpi_parse_sapic() 276 topology_register_apic((processor->id << 8) | processor->eid,/* APIC ID */ in acpi_parse_sapic() [all …]
|
| /linux/Documentation/core-api/ |
| 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 …]
|
| /linux/Documentation/staging/ |
| A D | remoteproc.rst | 39 Boot a remote processor (i.e. load its firmware, power it on, ...). 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, 123 initialization of the remote processor. 127 the registration of the remote processor. 155 a new remote processor device is probed. 244 if the remote processor is accessing memory directly). [all …]
|
| A D | rpmsg.rst | 14 Modern SoCs typically employ heterogeneous remote processor devices in 26 multimedia tasks from the main application processor. 35 resources on behalf of the remote processor, etc..). 81 one becomes available (i.e. until the remote processor consumes 99 The message will then be sent to the remote processor to which the 105 one becomes available (i.e. until the remote processor consumes 124 The message will then be sent to the remote processor to which the 130 one becomes available (i.e. until the remote processor consumes 166 The message will then be sent to the remote processor to which the 182 sends a message across to the remote processor, using source and [all …]
|
| /linux/drivers/hwmon/occ/ |
| 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
|