summaryrefslogtreecommitdiff
path: root/libs/gui/BufferQueueThreadState.cpp
diff options
context:
space:
mode:
author Vaibhav Devmurari <vdevmurari@google.com> 2024-07-16 13:17:33 +0000
committer Vaibhav Devmurari <vdevmurari@google.com> 2024-07-17 14:06:18 +0000
commitbffa940e939198aa5b9828912a928b072021beab (patch)
tree27c44ca0f05d3911275cbd873b9e80e78e119a6a /libs/gui/BufferQueueThreadState.cpp
parent2befa462eea2ca0be3b4872130109bd2b47aa4be (diff)
Remove notifyConfigurationChanged listener and policy calls
We found that notifyConfigurationChanged and input devices changed are synonymous for most use cases. From WM perspective the configuration can possibly change due to input device added/removed and hence we had the concept of configuration changed which was called when "device scan" was finished. But we realized configuration change can occur after a device is added/removed like associated display changes, keyboard type changes, etc. So, we think using input devices changed callback is better, making notifyConfigurationChanged callback not necessary. With this change, we remove: - notifyConfigurationChanged policy call - notifyConfigurationChanged listener calls in inputflinger - Call configuration change to WM on input devices changed - Move any logic on notifyConfigurationChanged listenr call to notifyInputDeviceChanged Bug: 245989146 Test: atest inputflinger_tests Flag: EXEMPT refactor Change-Id: Id30e8f1f24aa7206e3eacba88618ff2f48cda014
Diffstat (limited to 'libs/gui/BufferQueueThreadState.cpp')
0 files changed, 0 insertions, 0 deletions