There's at least one instance where the completion waited on in
dmc_notify() never happened. This happened because the mode stored in
"vop->crtc.hwmode" didn't match the current hardware mode while we're in
the middle of a resolution change.
We've got a fix for the above problem (see
CL:Ic78730293ba2d8d6c27ee833d27c519b59c6b717) but it also seems wise to
add a timeout here for extra safety.
BUG=chrome-os-partner:48332
TEST=Without above CL see printout; can't reproduce hang anymore.
Change-Id: I174167994d9c6f0df4cf9bde0a7bf485f7f92a28
Signed-off-by: Douglas Anderson <dianders@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/316661
Reviewed-by: Derek Basehore <dbasehore@chromium.org>
712908fec2