Home
last modified time | relevance | path

Searched refs:coupled (Results 1 – 16 of 16) sorted by relevance

/Linux-v4.19/drivers/cpuidle/
Dcoupled.c159 int n = dev->coupled->online_count; in cpuidle_coupled_parallel_barrier()
214 static inline void cpuidle_coupled_set_ready(struct cpuidle_coupled *coupled) in cpuidle_coupled_set_ready() argument
216 atomic_add(MAX_WAITING_CPUS, &coupled->ready_waiting_counts); in cpuidle_coupled_set_ready()
234 inline int cpuidle_coupled_set_not_ready(struct cpuidle_coupled *coupled) in cpuidle_coupled_set_not_ready() argument
239 all = coupled->online_count | (coupled->online_count << WAITING_BITS); in cpuidle_coupled_set_not_ready()
240 ret = atomic_add_unless(&coupled->ready_waiting_counts, in cpuidle_coupled_set_not_ready()
252 static inline int cpuidle_coupled_no_cpus_ready(struct cpuidle_coupled *coupled) in cpuidle_coupled_no_cpus_ready() argument
254 int r = atomic_read(&coupled->ready_waiting_counts) >> WAITING_BITS; in cpuidle_coupled_no_cpus_ready()
264 static inline bool cpuidle_coupled_cpus_ready(struct cpuidle_coupled *coupled) in cpuidle_coupled_cpus_ready() argument
266 int r = atomic_read(&coupled->ready_waiting_counts) >> WAITING_BITS; in cpuidle_coupled_cpus_ready()
[all …]
DMakefile7 obj-$(CONFIG_ARCH_NEEDS_CPU_IDLE_COUPLED) += coupled.o
/Linux-v4.19/Documentation/devicetree/bindings/regulator/
Dregulator.txt76 - regulator-coupled-with: Regulators with which the regulator
77 is coupled. The linkage is 2-way - all coupled regulators should be linked
78 with each other. A regulator should not be coupled with its supplier.
79 - regulator-coupled-max-spread: Max spread between voltages of coupled regulators
/Linux-v4.19/Documentation/devicetree/bindings/interrupt-controller/
Darm,nvic.txt3 The NVIC provides an interrupt controller that is tightly coupled to
/Linux-v4.19/include/linux/
Dcpuidle.h95 struct cpuidle_coupled *coupled; member
/Linux-v4.19/Documentation/sound/soc/
Doverview.rst11 * Codec drivers were often tightly coupled to the underlying SoC
/Linux-v4.19/Documentation/hwmon/
Dlm8355 secondary chips coupled with another chip such as an IT8705F or similar
/Linux-v4.19/Documentation/devicetree/bindings/leds/
Dcommon.txt10 have to be tightly coupled with the LED device binding. They are represented
/Linux-v4.19/drivers/bus/
DKconfig53 cores. This bus is for per-CPU tightly coupled devices such as the
/Linux-v4.19/Documentation/scheduler/
Dsched-nice-design.txt9 support was historically coupled to timeslice length, and timeslice
/Linux-v4.19/Documentation/power/regulator/
Dconsumer.txt156 Bespoke or tightly coupled drivers may want to directly control regulator
/Linux-v4.19/Documentation/virtual/kvm/
Dvcpu-requests.rst266 even the request-less VCPU kick is coupled with the same
/Linux-v4.19/Documentation/gpu/
Di915.rst111 to do atomic vsync'ed updates of all this state and also tightly coupled
/Linux-v4.19/Documentation/driver-api/gpio/
Dlegacy.rst447 A GPIO controller on a SOC might be tightly coupled with the pinctrl
/Linux-v4.19/Documentation/cgroup-v1/
Dcpusets.txt260 and with tightly coupled, long running, massively parallel scientific
/Linux-v4.19/drivers/video/fbdev/
DKconfig2252 and could also have been called by other names when coupled with