Android6.0 按键流程（二）KeyboardInputMapper扫描码转成键盘码

在上一篇博客中，我们详细分析了InputReader中读取设备事件，到processEventsLocked函数处理事件（包括设备事件，设备添加、删除等），再到ProcessEventsForDeviceLocked处理设备事件，最后到InputDevice的process函数，去遍历各个InputMapper执行process函数。

今天我们继续从这里开始分析，Input设备有很多种类，其消息格式各不相同，因此就有很多InputMapper对各个不同的RawEvent进行处理。

我们今天主要从按键的KeyboardInputMapper来讲解。

 

一、KeyboardInputMapper

下面我们主要从按键，比如音量键、power键的这个InputMapper说起：

void KeyboardInputMapper::process(const RawEvent* rawEvent) {
    switch (rawEvent->type) {
		
    case EV_KEY: {
        int32_t scanCode = rawEvent->code;
        int32_t usageCode = mCurrentHidUsage;
        mCurrentHidUsage = 0;

        if (isKeyboardOrGamepadKey(scanCode)) {
            int32_t keyCode;
            uint32_t flags;
            if (getEventHub()->mapKey(getDeviceId(), scanCode, usageCode, &keyCode, &flags)) {//扫描码对应成按键码
                keyCode = AKEYCODE_UNKNOWN;
                flags = 0;
            }
            processKey(rawEvent->when, rawEvent->value != 0, keyCode, scanCode, flags);
        }
        break;
    }
    case EV_MSC: {
        if (rawEvent->code == MSC_SCAN) {
            mCurrentHidUsage = rawEvent->value;
        }
        break;
    }
    case EV_SYN: {
        if (rawEvent->code == SYN_REPORT) {
            mCurrentHidUsage = 0;
        }
    }
    }
}

 

1.1 EventHub的mapKey函数

我们先来看下EventHub的mapKey函数，这个函数中outKeycode是入参，但是传的是指针，会往里面写值。

 

status_t EventHub::mapKey(int32_t deviceId, int32_t scanCode, int32_t usageCode,
        int32_t* outKeycode, uint32_t* outFlags) const {
    AutoMutex _l(mLock);
    Device* device = getDeviceLocked(deviceId);

    if (device) {
        // Check the key character map first.
        sp<KeyCharacterMap> kcm = device->getKeyCharacterMap();
        if (kcm != NULL) {
            if (!kcm->mapKey(scanCode, usageCode, outKeycode)) {
                    scanCode, *outKeycode);
                *outFlags = 0;
                return NO_ERROR;
            }
        }

        // Check the key layout next.
        if (device->keyMap.haveKeyLayout()) {
            if (!device->keyMap.keyLayoutMap->mapKey(
                    scanCode, usageCode, outKeycode, outFlags)) {
                return NO_ERROR;
            }
        }
    }

    *outKeycode = 0;
    *outFlags = 0;
    return NAME_NOT_FOUND;
}

我们看到还是通过device中的成员变量，由此可知肯定是在EventHub的openDeviceLocked函数中，

 

 

    status_t keyMapStatus = NAME_NOT_FOUND;
    if (device->classes & (INPUT_DEVICE_CLASS_KEYBOARD | INPUT_DEVICE_CLASS_JOYSTICK)) {
        // Load the keymap for the device.
        keyMapStatus = loadKeyMapLocked(device);
    }

果然在openDeviceLocked中有上面这段代码。

status_t EventHub::loadKeyMapLocked(Device* device) {
    return device->keyMap.load(device->identifier, device->configuration);
}

再来看下load函数，先通过deviceConfiguration获取keyLayoutName，deviceConfiguration肯定也是前面openDeviceLocked的时候创建的，这里就不分析了。

 

status_t KeyMap::load(const InputDeviceIdentifier& deviceIdenfifier,
        const PropertyMap* deviceConfiguration) {
    // Use the configured key layout if available.
    if (deviceConfiguration) {
        String8 keyLayoutName;
        if (deviceConfiguration->tryGetProperty(String8("keyboard.layout"),
                keyLayoutName)) {//通过deviceConfiguration获取keyLayoutName
            status_t status = loadKeyLayout(deviceIdenfifier, keyLayoutName);
            if (status == NAM