Searched refs:oneshot (Results 1 – 12 of 12) sorted by relevance
47 int oneshot);224 static int uv__signal_register_handler(int signum, int oneshot) { in uv__signal_register_handler() argument234 if (oneshot) in uv__signal_register_handler()355 int oneshot) { in uv__signal_start() argument392 (!oneshot && (first_handle->flags & UV_SIGNAL_ONE_SHOT))) { in uv__signal_start()393 err = uv__signal_register_handler(signum, oneshot); in uv__signal_start()402 if (oneshot) in uv__signal_start()
40 int oneshot);196 int oneshot) { in uv__signal_start() argument220 if (oneshot) in uv__signal_start()
6 Type=oneshot
9 Type=oneshot
7 Type=oneshot
8 Type=oneshot
12 Type=oneshot
19 oneshot
10978 the oneshot timer. Due to a wrong assumption concerning the behavior10992 the oneshot counter is correct. I also tried to use the function10996 Another problem treated in the fix is that if the oneshot timer/counter11008 be applied to the SAMA5 oneshot time since the drivers are identical.11013 be applied to the SAM3/4 oneshot time since the drivers are identical.11287 PWM, oneshot, free-running.... From ziggurat29.11802 - Use the oneshot timer with optional entropy to measure CPU load if11861 - Add oneshot timer lower half interface definition.11862 - Add an upper-half, oneshot timer character driver.11874 - Add a simulated oneshot lowerhalf driver.[all …]
2286 EVP_R_ONLY_ONESHOT_SUPPORTED:177:only oneshot supported
8113 framework needn't accumulate the data for oneshot drivers.