Update TouchInputMapper to support new VirtualNavigationTouchpad.
This change propagates type associations to InputDevice.cpp. The type associations are used there to define the device type for touch input mapper to use. This is required because of the virtual nature of the navigation touchpad the implementation can't rely on idc files. Design doc: http://go/virtual-touchpad Test: atest cts/tests/tests/hardware/src/android/hardware/input/cts/tests/VirtualNavigationTouchpadTest Test: atest frameworks/native/services/inputflinger/tests/InputReader_test.cpp Bug: 252767726 Change-Id: Ia4252460c16deb093d61b059e5030d902a4c9a2c
Loading
Please register or sign in to comment