| /Linux-v5.10/drivers/iio/light/ |
| D | lm3533-als.c | 311 static inline u8 lm3533_als_get_threshold_reg(unsigned nr, bool raising) in lm3533_als_get_threshold_reg() argument
313 u8 offset = !raising; in lm3533_als_get_threshold_reg()
319 bool raising, u8 *val) in lm3533_als_get_threshold() argument
328 reg = lm3533_als_get_threshold_reg(nr, raising); in lm3533_als_get_threshold()
337 bool raising, u8 val) in lm3533_als_set_threshold() argument
347 reg = lm3533_als_get_threshold_reg(nr, raising); in lm3533_als_set_threshold()
348 reg2 = lm3533_als_get_threshold_reg(nr, !raising); in lm3533_als_set_threshold()
361 if ((raising && (val < val2)) || (!raising && (val > val2))) { in lm3533_als_set_threshold()
382 u8 raising; in lm3533_als_get_hysteresis() local
392 ret = lm3533_als_get_threshold(indio_dev, nr, true, &raising); in lm3533_als_get_hysteresis()
[all …]
|
| /Linux-v5.10/block/ |
| D | bfq-iosched.c | 54 * mainly, by raising the weight of the queue. So, for brevity, we
55 * call just weight-raising periods the time periods during which a
73 * weight-raising for interactive queues.
271 * When configured for computing the duration of the weight-raising
285 * weight raising to interactive applications.
313 * BFQ uses the above-detailed, time-based weight-raising mechanism to
317 * raising. These applications have basically no benefit from being
328 * finish explaining how the duration of weight-raising for
332 * raising is dynamically adjusted, as a function of the estimated
342 * duration of weight-raising for at least one class of I/O-bound
[all …]
|
| D | bfq-iosched.h | 320 /* current maximum weight-raising time for this queue */
331 * Start time of the current weight-raising period if
333 * finish time of the last weight-raising period.
697 /* maximum duration of a weight-raising period (jiffies) */
700 /* Maximum weight-raising duration for soft real-time processes */
703 * Minimum idle period after which weight-raising may be
709 * weight-raising may be reactivated for an already busy async
718 * for computing the maximum duration of weight raising
|
| /Linux-v5.10/tools/testing/selftests/powerpc/signal/ |
| D | sigfuz.c | 12 * This test works raising a signal and calling sigreturn interleaved with
278 printf("\t-b\t Mess with TM before raising a SIGUSR1 signal\n"); in show_help()
279 printf("\t-a\t Mess with TM after raising a SIGUSR1 signal\n"); in show_help()
|
| /Linux-v5.10/ipc/ |
| D | namespace.c | 158 * So dropping the refcount, and raising the refcount when
161 * (Clearly, a task raising the refcount on its own ipc_ns
|
| /Linux-v5.10/Documentation/devicetree/bindings/gpio/ |
| D | netxbig-gpio-ext.txt | 8 - enable-gpio: latches the new configuration (address, data) on raising edge.
|
| /Linux-v5.10/drivers/atm/ |
| D | zeprom.h | 17 #define ZEPROM_SK 0x80000000 /* strobe (probably on raising edge) */
|
| /Linux-v5.10/drivers/media/dvb-frontends/ |
| D | s5h1420.h | 24 u8 cdclk_polarity:1; /* 1 == falling edge, 0 == raising edge */
|
| /Linux-v5.10/tools/lib/perf/ |
| D | cpumap.c | 118 "Consider raising MAX_NR_CPUS\n", MAX_NR_CPUS); in perf_cpu_map__read()
213 "Consider raising MAX_NR_CPUS\n", MAX_NR_CPUS); in perf_cpu_map__new()
|
| /Linux-v5.10/include/linux/ |
| D | lp.h | 86 #define LP_PSTROBE 0x01 /* short high output on raising edge */
|
| /Linux-v5.10/arch/arm64/kernel/ |
| D | sys_compat.c | 105 * if not implemented, rather than raising SIGILL. This in compat_arm_syscall()
|
| /Linux-v5.10/Documentation/accounting/ |
| D | delay-accounting.rst | 22 important tasks could be a trigger for raising its corresponding priority.
|
| /Linux-v5.10/drivers/crypto/caam/ |
| D | Kconfig | 82 raising an interrupt, in the range 1-255. Note that a selection
|
| /Linux-v5.10/drivers/net/ethernet/intel/ixgb/ |
| D | ixgb_ee.c | 82 * and then raising and then lowering the clock (the SK bit controls in ixgb_shift_out_bits()
84 * by setting "DI" to "0" and then raising and then lowering the clock. in ixgb_shift_out_bits()
121 * in from the EEPROM. Bits are "shifted in" by raising the clock input to in ixgb_shift_in_bits()
276 * signal that the command has been completed by raising the DO signal. in ixgb_wait_eeprom_command()
|
| /Linux-v5.10/arch/m68k/coldfire/ |
| D | intc.c | 95 * interrupt controller. That is, the device raising the interrupt can also
|
| /Linux-v5.10/drivers/scsi/ufs/ |
| D | ufs_quirks.h | 46 * the Host UniPro goes into bad state without raising the DFES error
|
| /Linux-v5.10/Documentation/devicetree/bindings/mailbox/ |
| D | arm,mhu.yaml | 27 be associated with a type of event that can contribute to raising the
|
| /Linux-v5.10/security/apparmor/ |
| D | resource.c | 100 * Control raising the processes hard limit.
|
| /Linux-v5.10/Documentation/arm/ |
| D | kernel_mode_neon.rst | 70 software assistance, it signals the kernel by raising an undefined instruction
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | rtc.rst | 50 for...) It can also function as a 24hr alarm, raising IRQ 8 when the
|
| /Linux-v5.10/Documentation/scheduler/ |
| D | sched-energy.rst | 261 result in raising the OPP of the entire performance domain, and that will
267 smaller than the cost of raising the OPP on the little CPUs for all the other
|
| /Linux-v5.10/Documentation/block/ |
| D | bfq-iosched.rst | 215 throughput. For brevity, we call just "weight-raising" the whole
217 particular, BFQ provides a milder form of weight-raising for
|
| /Linux-v5.10/arch/powerpc/kvm/ |
| D | book3s_hv_rm_xics.c | 208 * flag when raising CPPR, so we need to set it back here if an in icp_rm_try_update()
641 * The processor is raising its priority, this can result in xics_rm_h_cppr()
|
| /Linux-v5.10/include/uapi/linux/ |
| D | capability.h | 285 /* Allow raising priority and setting priority on other (different
|
| /Linux-v5.10/drivers/watchdog/ |
| D | watchdog_core.c | 51 * raising the initcall level of the watchdog driver is a solution.
|
