/linux-6.14.4/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-6.14.4/fs/tests/ |
D | exec_kunit.c | 82 /* But raising it another pointer * 4 will provide space for 1 more pointer. */ 89 /* Raising rlim_stack / 4 to _STK_LIM / 4 * 3 will see more space. */ 96 /* But raising it any further will see no increase. */
|
/linux-6.14.4/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 | 341 /* current maximum weight-raising time for this queue */ 352 * Start time of the current weight-raising period if 354 * finish time of the last weight-raising period. 772 /* Maximum weight-raising duration for soft real-time processes */ 775 * Minimum idle period after which weight-raising may be 781 * weight-raising may be reactivated for an already busy async 790 * for computing the maximum duration of weight raising
|
/linux-6.14.4/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-6.14.4/Documentation/devicetree/bindings/gpio/ |
D | netxbig-gpio-ext.txt | 8 - enable-gpio: latches the new configuration (address, data) on raising edge.
|
/linux-6.14.4/drivers/atm/ |
D | zeprom.h | 17 #define ZEPROM_SK 0x80000000 /* strobe (probably on raising edge) */
|
/linux-6.14.4/ipc/ |
D | namespace.c | 193 * So dropping the refcount, and raising the refcount when 196 * (Clearly, a task raising the refcount on its own ipc_ns
|
/linux-6.14.4/drivers/media/dvb-frontends/ |
D | s5h1420.h | 24 u8 cdclk_polarity:1; /* 1 == falling edge, 0 == raising edge */
|
/linux-6.14.4/Documentation/ABI/testing/ |
D | sysfs-devices-xenbus | 40 basis and is known not to be malicious on purpose. Raising
|
D | sysfs-class-power-ltc4162l | 74 until some external power-supply is attached raising the input
|
/linux-6.14.4/tools/testing/selftests/kvm/ |
D | kvm_create_max_vcpus.c | 54 * try raising the limits if needed. in main()
|
/linux-6.14.4/include/linux/ |
D | lp.h | 86 #define LP_PSTROBE 0x01 /* short high output on raising edge */
|
/linux-6.14.4/arch/arm64/kernel/ |
D | sys_compat.c | 104 * if not implemented, rather than raising SIGILL. This in compat_arm_syscall()
|
/linux-6.14.4/include/ufs/ |
D | ufs_quirks.h | 37 * the Host UniPro goes into bad state without raising the DFES error
|
/linux-6.14.4/drivers/crypto/caam/ |
D | Kconfig | 82 raising an interrupt, in the range 1-255. Note that a selection
|
/linux-6.14.4/arch/m68k/coldfire/ |
D | intc.c | 95 * interrupt controller. That is, the device raising the interrupt can also
|
/linux-6.14.4/Documentation/accounting/ |
D | delay-accounting.rst | 26 important tasks could be a trigger for raising its corresponding priority.
|
/linux-6.14.4/Documentation/devicetree/bindings/mailbox/ |
D | arm,mhu.yaml | 27 be associated with a type of event that can contribute to raising the
|
/linux-6.14.4/tools/testing/selftests/signal/ |
D | mangle_uc_sigmask.c | 168 * Raising USR2 in handler_verify_ucontext is redundant since it in main()
|
/linux-6.14.4/sound/soc/starfive/ |
D | jh7110_tdm.c | 53 /* tx raising and rx falling */ 55 /* tx falling and rx raising */
|
/linux-6.14.4/security/apparmor/ |
D | resource.c | 111 * Control raising the processes hard limit.
|
/linux-6.14.4/Documentation/arch/arm/ |
D | kernel_mode_neon.rst | 70 software assistance, it signals the kernel by raising an undefined instruction
|
/linux-6.14.4/Documentation/admin-guide/ |
D | rtc.rst | 50 for...) It can also function as a 24hr alarm, raising IRQ 8 when the
|
/linux-6.14.4/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
|