| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| | |
https://android.googlesource.com/platform/frameworks/native into cm-13.0
Android 6.0.1 release 22
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
SurfaceFlinger shouldn't be limited to little cores exclusively, as the
binder threads should be placed on big cores when they are in the
critical path for a RenderThread.
bug 25745866
Change-Id: I9fb65f6d951733f91b4735ff27018411b58b2bfb
|
|/
|
|
|
|
|
|
| |
Add DisplayUtils class which uses the custom implementations
of ExLayer, ExSurfaceFlinger, ExHWComposer,
and ExVirtualDisplaySurface classes if needed
Change-Id: Ibdd8da5d3d0d602f42b76a15d0994c6aa98bee3f
|
|
|
|
|
| |
Bug: 19083585
Change-Id: I355491de945590f43c82bdcb7968b01b4bff6e06
|
|
|
|
|
|
|
|
| |
Dumps the current DispSync state.
Bug 14651879
Change-Id: Ide4e6dbd58b117bc1a6b97b57d10cd92ec86dc84
|
|
|
|
|
|
|
|
|
|
| |
SF can spawn threads (indirectly) during initialization
and we want those to be spawned at URGENT_DISPLAY_PRIORITY
(in theory they should set their own, but some code lives
in vendor libraries and doesn't).
Bug: 10430209
Change-Id: I5b3a8f979297de287614c8eafd8267bef1176e4b
|
|
|
|
|
|
|
|
|
|
| |
it used to spawn its own thread and return the main thread
to the binder thread pool -- this was confusing the naming
of things in the kernel.
Bug: 10331839
Change-Id: I2d13a6d73409a38109300fcbe6a04b4c41cb5d00
|
|
Change-Id: Ic65434a26c7fed1699abf0851fec6faa40e09c0c
|