[Ozone-DRM] Modeset when re-mapping windows to controllers

[Ozone-DRM] Modeset when re-mapping windows to controllers

This fixes an issue where the surface associated with a window thinks it
can submit a buffer, but the controller is waiting for a page flip event
to finish. This issue is triggered in the following scenario:

- surface1 mapped to display1
- surface2 mapped to display2
- surface2 page flips a buffer on display2
- surface1 is re-mapped to display2
- surface2 is re-mapped to display1
- surface1 had no pending buffers, so it thinks it is fine to schedule a
  page flip on display2
- display2 fails to page flip since it is still waiting for the callback
  from surface2

We had considered using a queue internally, though that would have
complicated the logic. Since changing display configuration is a rare
event we decided it would be simpler to just modeset at this point even
if modesetting would take longer.

BUG=511446, 529806
Committed: https://crrev.com/569ff0f367864bc65b8abaaab4dec1e57d25ac93
Cr-Commit-Position: refs/heads/master@{#348496}

[dnicoara, 2015-09-10 22:22:11]

The CQ bit was checked by dnicoara@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-09-10 22:22:39]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1327413003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1327413003/1

[dnicoara, 2015-09-10 22:23:49]

dnicoara@chromium.org changed reviewers:
+ alexst@chromium.org

[dnicoara, 2015-09-10 22:23:50]

This is required, but still doesn't fix the last corner case. I can still end up
in a state where the page flip fails even though it looks like there are no
pending page flips.

This is the page flip error:
[6571:6571:0910/175811:ERROR:hardware_display_plane_manager_legacy.cc(59)]
Cannot page flip: crtc=26 framebuffer=45 is_sync=0: Device or resource busy

[commit-bot: I haz the power, 2015-09-10 23:06:39]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-09-10 23:06:39]

Dry run: Try jobs failed on following builders:
  linux_chromium_chromeos_ozone_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[dnicoara, 2015-09-10 23:47:17]

The CQ bit was checked by dnicoara@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-09-10 23:47:43]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1327413003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1327413003/20001

[commit-bot: I haz the power, 2015-09-11 00:09:25]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-09-11 00:09:26]

Dry run: This issue passed the CQ dry run.

[alexst (slow to review), 2015-09-11 19:32:55]

lgtm

[dnicoara, 2015-09-11 22:01:46]

The CQ bit was checked by dnicoara@chromium.org

[commit-bot: I haz the power, 2015-09-11 22:02:52]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1327413003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1327413003/20001

[commit-bot: I haz the power, 2015-09-11 22:12:13]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-09-11 22:12:49]

Patchset 2 (id:??) landed as
https://crrev.com/569ff0f367864bc65b8abaaab4dec1e57d25ac93
Cr-Commit-Position: refs/heads/master@{#348496}

[commit-bot: I haz the power, 2015-09-23 12:26:45]

Patchset 2 (id:??) landed as
https://crrev.com/569ff0f367864bc65b8abaaab4dec1e57d25ac93
Cr-Commit-Position: refs/heads/master@{#348496}