Home
last modified time | relevance | path

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

/Linux-v5.4/drivers/cpuidle/
Dcoupled.c150 int n = dev->coupled->online_count; in cpuidle_coupled_parallel_barrier()
205 static inline void cpuidle_coupled_set_ready(struct cpuidle_coupled *coupled) in cpuidle_coupled_set_ready() argument
207 atomic_add(MAX_WAITING_CPUS, &coupled->ready_waiting_counts); in cpuidle_coupled_set_ready()
225 inline int cpuidle_coupled_set_not_ready(struct cpuidle_coupled *coupled) in cpuidle_coupled_set_not_ready() argument
230 all = coupled->online_count | (coupled->online_count << WAITING_BITS); in cpuidle_coupled_set_not_ready()
231 ret = atomic_add_unless(&coupled->ready_waiting_counts, in cpuidle_coupled_set_not_ready()
243 static inline int cpuidle_coupled_no_cpus_ready(struct cpuidle_coupled *coupled) in cpuidle_coupled_no_cpus_ready() argument
245 int r = atomic_read(&coupled->ready_waiting_counts) >> WAITING_BITS; in cpuidle_coupled_no_cpus_ready()
255 static inline bool cpuidle_coupled_cpus_ready(struct cpuidle_coupled *coupled) in cpuidle_coupled_cpus_ready() argument
257 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-v5.4/Documentation/devicetree/bindings/interrupt-controller/
Darm,nvic.txt3 The NVIC provides an interrupt controller that is tightly coupled to
/Linux-v5.4/include/linux/
Dcpuidle.h99 struct cpuidle_coupled *coupled; member
/Linux-v5.4/Documentation/sound/soc/
Doverview.rst11 * Codec drivers were often tightly coupled to the underlying SoC
/Linux-v5.4/Documentation/hwmon/
Dlm83.rst67 secondary chips coupled with another chip such as an IT8705F or similar
/Linux-v5.4/Documentation/driver-api/pm/
Dcpuidle.rst232 entries in the :c:member:`states` array represent "coupled" idle states (that
235 to be the index of an idle state that is not "coupled" (that is, one that can be
244 are no "coupled" idle state entries in the driver's :c:member:`states` array,
/Linux-v5.4/Documentation/scheduler/
Dsched-nice-design.rst13 support was historically coupled to timeslice length, and timeslice
/Linux-v5.4/drivers/bus/
DKconfig63 cores. This bus is for per-CPU tightly coupled devices such as the
/Linux-v5.4/Documentation/devicetree/bindings/leds/
Dcommon.txt10 have to be tightly coupled with the LED device binding. They are represented
/Linux-v5.4/Documentation/power/regulator/
Dconsumer.rst165 Bespoke or tightly coupled drivers may want to directly control regulator
/Linux-v5.4/Documentation/virt/kvm/
Dvcpu-requests.rst266 even the request-less VCPU kick is coupled with the same
/Linux-v5.4/Documentation/gpu/
Di915.rst108 to do atomic vsync'ed updates of all this state and also tightly coupled
/Linux-v5.4/Documentation/driver-api/gpio/
Dlegacy.rst447 A GPIO controller on a SOC might be tightly coupled with the pinctrl
/Linux-v5.4/Documentation/admin-guide/cgroup-v1/
Dcpusets.rst262 and with tightly coupled, long running, massively parallel scientific
/Linux-v5.4/drivers/video/fbdev/
DKconfig2197 and could also have been called by other names when coupled with