Input系统学习-----InputDispatcher中的looper

InputReader负责获取设备的输入数据，然后发给InputDispatcher去处理，为了让2个处理独立起来，不相互影响，它们是在不同的线程中执行的，

InputDispatcher里的threadLoop方法是继承的Thread的方法，会在一个while中不停的调用起来，

不停的调用，会不会太占用资源？

bool InputDispatcherThread::threadLoop() {
    mDispatcher->dispatchOnce();
    return true;
}

查看dispatchOnce方法，里面使用了  mLooper->pollOnce(timeoutMillis);来进行阻塞，就避免了不断的执行循环，

void InputDispatcher::dispatchOnce() {
    nsecs_t nextWakeupTime = LONG_LONG_MAX;
    { // acquire lock
        AutoMutex _l(mLock);
        mDispatcherIsAliveCondition.broadcast();

        // Run a dispatch loop if there are no pending commands.
        // The dispatch loop might enqueue commands to run afterwards.
        if (!haveCommandsLocked()) {
            dispatchOnceInnerLocked(&nextWakeupTime);
        }

        // Run all pending commands if there are any.
        // If any commands were run then force the next poll to wake up immediately.
        if (runCommandsLockedInterruptible()) {
            nextWakeupTime = LONG_LONG_MIN;
        }
    } // release lock

    // Wait for callback or timeout or wake.  (make sure we round up, not down)
    nsecs_t currentTime = now();
    int timeoutMillis = toMillisecondTimeoutDelay(currentTime, nextWakeupTime);
    mLooper->pollOnce(timeoutMillis);
}

这里阻塞住了，我们可以猜想，InputReader传送数据过来的时候，就不再阻塞，

InputReader传送touch事件的时候，调用到InputDispatcher中的notifyMotion方法，

void InputDispatcher::notifyMotion(const NotifyMotionArgs* args) {

        // Just enqueue a new motion event.
        MotionEntry* newEntry = new MotionEntry(args->eventTime,
                args->deviceId, args->source, policyFlags,
                args->action, args->actionButton, args->flags,
                args->metaState, args->buttonState,
                args->edgeFlags, args->xPrecision, args->yPrecision, args->downTime,
                args->displayId,
                args->pointerCount, args->pointerProperties, args->pointerCoords, 0, 0);

        needWake = enqueueInboundEventLocked(newEntry);
        mLock.unlock();
    } // release lock

    if (needWake) {
        mLooper->wake();
    }

可以看到。里面调用了  mLooper->wake();

就解除了dispatchOnce中的looper阻塞，在handler的相关调用中，Looper都隐藏的很深，几乎是透明的存在，看不到其身影，而这里，Looper现身了，不再隐藏，这里直接使用了其阻塞和唤醒功能来实现2个线程间的交互。