commit b2aff84fcf453b4524bbd4c628d00ae0f0d93f4c
author Arpit Singh <arpitks@google.com> Tue Sep 26 10:11:34 2023 +0000
committer Arpit Singh <arpitks@google.com> Mon Oct 02 13:55:43 2023 +0000
tree 8bad5d91eb7ca2aa4a9ae928ae8df0002be92d3e
parent 9e8407669e0b419379c60341c604e36cd4be5f9e

Add flag to mark key usage code as a fallback mapping

We don't yet have a way to determine if a device can actually report a
usage code. Adding a flag to mark usage code as fallback only mapping.

Bug: 297094448
Test: atest inputflinger_tests
Change-Id: I137113d0dc9a1c8abf523b96942486be176d0240

libs/input/KeyLayoutMap.cpp

diff --git a/libs/input/KeyLayoutMap.cpp b/libs/input/KeyLayoutMap.cpp
index ddc9ea4..3c1ae3e 100644
--- a/libs/input/KeyLayoutMap.cpp
+++ b/libs/input/KeyLayoutMap.cpp
@@ -250,7 +250,7 @@
 std::vector<int32_t> KeyLayoutMap::findUsageCodesForKey(int32_t keyCode) const {
     std::vector<int32_t> usageCodes;
     for (const auto& [usageCode, key] : mKeysByUsageCode) {
-        if (keyCode == key.keyCode) {
+        if (keyCode == key.keyCode && !(key.flags & POLICY_FLAG_FALLBACK_USAGE_MAPPING)) {
             usageCodes.push_back(usageCode);
         }
     }