| commit | 52854972c945d9d48ad4e391da08dc733202ed00 | |
| author | dnicoara <dnicoara@chromium.org> | |
| Wed, 3 Jun 2015 13:09:40 +0000 (3 06:09 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Wed, 3 Jun 2015 13:10:40 +0000 (3 13:10 +0000) | ||
| tree | e0b203a359d9ffbaa3108467c66d35adfedd62f8 | treesnapshot (tar.gz zip) |
| parent | 255913a791a398eed5c352fa3ac220be178cc772 | commitdiff |
Update Take/Release display control to async API
When switching from Chrome to Frecon, Frecon waits for the dbus reply to
take ownership of the DRM device. Since NativeDisplayDelegate calls may
be async, the current code responds back to Frecon at the same time as
the IPC to release master happens. As a consequence it is possible that
Frecon tries to acquire master before Chrome releases it.
This change updates the NativeDisplayDelegate API to allow
asynchronously taking and releasing of the display control (DRM master)
and updates the console service provider to use the async API.
BUG=none
Review URL: https://codereview.chromium.org/1160973005
Cr-Commit-Position: refs/heads/master@{#332604}
When switching from Chrome to Frecon, Frecon waits for the dbus reply to
take ownership of the DRM device. Since NativeDisplayDelegate calls may
be async, the current code responds back to Frecon at the same time as
the IPC to release master happens. As a consequence it is possible that
Frecon tries to acquire master before Chrome releases it.
This change updates the NativeDisplayDelegate API to allow
asynchronously taking and releasing of the display control (DRM master)
and updates the console service provider to use the async API.
BUG=none
Review URL: https://codereview.chromium.org/1160973005
Cr-Commit-Position: refs/heads/master@{#332604}
16 files changed: