Home
last modified time | relevance | path

Searched full:raising (Results 1 – 25 of 204) sorted by relevance

123456789

/kernel/linux/linux-6.6/drivers/iio/light/
Dlm3533-als.c311 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 …]
/kernel/linux/linux-5.10/drivers/iio/light/
Dlm3533-als.c311 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 …]
/kernel/linux/linux-6.6/block/
Dbfq-iosched.c54 * 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 …]
Dbfq-iosched.h341 /* 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
/kernel/linux/linux-5.10/block/
Dbfq-iosched.c54 * 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 …]
Dbfq-iosched.h320 /* 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
/kernel/linux/linux-5.10/tools/testing/selftests/powerpc/signal/
Dsigfuz.c12 * 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()
/kernel/linux/linux-6.6/tools/testing/selftests/powerpc/signal/
Dsigfuz.c12 * 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()
/kernel/linux/linux-5.10/ipc/
Dnamespace.c158 * So dropping the refcount, and raising the refcount when
161 * (Clearly, a task raising the refcount on its own ipc_ns
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/gpio/
Dnetxbig-gpio-ext.txt8 - enable-gpio: latches the new configuration (address, data) on raising edge.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpio/
Dnetxbig-gpio-ext.txt8 - enable-gpio: latches the new configuration (address, data) on raising edge.
/kernel/linux/linux-6.6/drivers/atm/
Dzeprom.h17 #define ZEPROM_SK 0x80000000 /* strobe (probably on raising edge) */
/kernel/linux/linux-5.10/drivers/atm/
Dzeprom.h17 #define ZEPROM_SK 0x80000000 /* strobe (probably on raising edge) */
/kernel/linux/linux-6.6/drivers/media/dvb-frontends/
Ds5h1420.h24 u8 cdclk_polarity:1; /* 1 == falling edge, 0 == raising edge */
/kernel/linux/linux-5.10/drivers/media/dvb-frontends/
Ds5h1420.h24 u8 cdclk_polarity:1; /* 1 == falling edge, 0 == raising edge */
/kernel/linux/linux-6.6/ipc/
Dnamespace.c191 * So dropping the refcount, and raising the refcount when
194 * (Clearly, a task raising the refcount on its own ipc_ns
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-devices-xenbus40 basis and is known not to be malicious on purpose. Raising
Dsysfs-class-power-ltc4162l74 until some external power-supply is attached raising the input
/kernel/linux/linux-6.6/tools/testing/selftests/kvm/
Dkvm_create_max_vcpus.c56 * try raising the limits if needed. in main()
/kernel/linux/linux-5.10/tools/lib/perf/
Dcpumap.c118 "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()
/kernel/linux/linux-5.10/tools/testing/selftests/kvm/
Dkvm_create_max_vcpus.c56 * try raising the limits if needed. in main()
/kernel/linux/linux-6.6/include/linux/
Dlp.h86 #define LP_PSTROBE 0x01 /* short high output on raising edge */
/kernel/linux/linux-5.10/include/linux/
Dlp.h86 #define LP_PSTROBE 0x01 /* short high output on raising edge */
/kernel/linux/linux-6.6/arch/arm64/kernel/
Dsys_compat.c104 * if not implemented, rather than raising SIGILL. This in compat_arm_syscall()
/kernel/linux/linux-5.10/Documentation/accounting/
Ddelay-accounting.rst22 important tasks could be a trigger for raising its corresponding priority.

123456789