Searched full:deciding (Results 1 – 25 of 84) sorted by relevance
1234
9 * Idle state target residency threshold used for deciding whether or not to
18 round trip delay for the signals and is used for deciding on values
71 * starts deciding to set a new TPIDR2 between us reading and in tpidr2_present()
198 * @isolate: callback function that is responsible for deciding what to do with224 * @isolate: callback function that is responsible for deciding what to do with
27 any logic for deciding what voltage we should set regulators to28 any logic for deciding whether regulators (or internal SoC blocks)
26 the filesystem defers deciding the exact placement on the disk until all
75 * which case userspace is responsible for deciding on what bytes are signed.
83 /* Masks for deciding who handles the interrupt */
60 deciding whether to balance the regular zone. The first solution
108 /* after we give up on a socket we wait a while before deciding
12 or deciding where to place the workload within a compute cluster.
103 your system performs under each setting, before deciding on
156 * in deciding which irq_chip structure is used
142 * When deciding which sysfs attributes to support, look at the chip's
124 uses the -p (platform) argument as the main method of deciding which wrapper
103 Setting the activation size thresholds to large values will result in deciding
36 transactions or deciding who is allowed to talk on the bus (slave generated
56 * reset before deciding that something has gone wrong
332 * space. Callers are responsible for deciding what to do in xfs_ag_resv_init()
159 system memory resources or fail. In case of UMD deciding to fail a
91 Deciding when to start using a key is a performance issue. Deciding
66 * @update: Optional callback deciding whether or not to skip idle
24 Creating a gadget means deciding what configurations there will be
28 * before deciding the slave is not responding. 0 disables the
161 * to complete, deciding how long it is worth spinning is for is an in max_spin_store()