| /device/asus/flo/charger_touch/ |
| charger_touch.c | 103 static void event_loop(void) function
119 event_loop();
|
| /device/lge/mako/charger_touch/ |
| charger_touch.c | 103 static void event_loop(void) function
119 event_loop();
|
| /external/chromium/third_party/libevent/ |
| event.3 | 35 .Nm event_loop ,
95 .Fn "event_loop" "int flags"
411 .Nm event_loop
422 .Fn event_loop
426 .Fn event_loop
431 .Fn event_loop
436 .Fn event_loop
|
| event.h | 362 event_loop() flags
379 int event_loop(int);
397 The next event_loop() iteration after the given timer expires will
401 Subsequent invocations of event_loop() will proceed normally.
405 @see event_loop(), event_base_loop(), event_base_loopexit()
427 Abort the active event_loop() immediately.
429 event_loop() will abort the loop after the next event is completed;
433 Subsequent invocations of event_loop() will proceed normally.
447 Subsequent invocations of event_loop() will proceed normally.
[all...] |
| ChangeLog | 123 o update documentation of event_loop and event_base_loop; from Tani Hosokawa.
134 o Make kqueue have the same behavior as other backends when a signal is caught between event_add() and event_loop(). Previously, it would catch and ignore such signals.
|
| event.c | 399 return (event_loop(0));
459 event_loop(int flags) function
|
| /external/chromium_org/third_party/libevent/ |
| event.3 | 35 .Nm event_loop ,
95 .Fn "event_loop" "int flags"
411 .Nm event_loop
422 .Fn event_loop
426 .Fn event_loop
431 .Fn event_loop
436 .Fn event_loop
|
| event.h | 362 event_loop() flags
379 int event_loop(int);
397 The next event_loop() iteration after the given timer expires will
401 Subsequent invocations of event_loop() will proceed normally.
405 @see event_loop(), event_base_loop(), event_base_loopexit()
427 Abort the active event_loop() immediately.
429 event_loop() will abort the loop after the next event is completed;
433 Subsequent invocations of event_loop() will proceed normally.
447 Subsequent invocations of event_loop() will proceed normally.
[all...] |
| ChangeLog | 123 o update documentation of event_loop and event_base_loop; from Tani Hosokawa.
134 o Make kqueue have the same behavior as other backends when a signal is caught between event_add() and event_loop(). Previously, it would catch and ignore such signals.
|
| event.c | 399 return (event_loop(0));
459 event_loop(int flags) function
|
| /external/android-clat/ |
| clatd.c | 330 /* function: event_loop
334 void event_loop(const struct tun_data *tunnel) { function
351 logmsg(ANDROID_LOG_WARN,"event_loop/poll returned an error: %s",strerror(errno));
450 event_loop(&tunnel);
|
| /external/chromium/third_party/libevent/test/ |
| bench.c | 95 event_loop(EVLOOP_ONCE | EVLOOP_NONBLOCK);
108 event_loop(EVLOOP_ONCE | EVLOOP_NONBLOCK);
|
| regress.c | 662 event_loop(EVLOOP_NONBLOCK);
1298 event_loop(EVLOOP_ONCE);
1301 event_loop(EVLOOP_ONCE);
[all...] |
| /external/chromium_org/third_party/libevent/test/ |
| bench.c | 95 event_loop(EVLOOP_ONCE | EVLOOP_NONBLOCK);
108 event_loop(EVLOOP_ONCE | EVLOOP_NONBLOCK);
|
| regress.c | 662 event_loop(EVLOOP_NONBLOCK);
1298 event_loop(EVLOOP_ONCE);
1301 event_loop(EVLOOP_ONCE);
[all...] |
| /system/core/charger/ |
| charger.c | 931 static void event_loop(struct charger *charger) function
938 LOGV("[%lld] event_loop()\n", now);
1012 event_loop(charger);
|
