| commit | eb83011e1db18c15af48e143b4d85b2f8a8f19cb | [log] [tgz] |
|---|---|---|
| author | Prabir Pradhan <prabirmsp@google.com> | Tue Mar 05 03:54:00 2024 +0000 |
| committer | Cherrypicker Worker <android-build-cherrypicker-worker@google.com> | Fri Mar 15 03:31:52 2024 +0000 |
| tree | dfc62dd8c4c57d1effeec0590093e62ee4bddd4e | |
| parent | c0ed405f3f23972fa58f3af1e5e76593b651c7f1 [diff] |
PointerChoreographer: Do not call the policy with the lock held Since there is already precedent for InputReader to interact with the policy with its lock held, we must not do the same from other components, since it can result in deadlocks. In this CL, we ensure that the PointerChoreographer does not interact with the policy while holding its lock. The exception is the use of the factory method for PointerController, which is only part of the policy to work around dependency issues with graphics libraries. Bug: 327717240 Test: atest inputflinger_tests (cherry picked from https://googleplex-android-review.googlesource.com/q/commit:5a51a2280743605a51e2f9d632077e9297276520) Merged-In: Ib81d72898a212275d95f9d84d89a16e7172e108e Change-Id: Ib81d72898a212275d95f9d84d89a16e7172e108e