bad link is just one way modeset will fail. What's the plan for other ways? What's the plan for problems which can be represented in a driver-agnostic ways?

Overall it sounds like we wouldn't really be solving a problem but just making things more complicated...

This isn't for modeset fails, rather, it's for link failures during steady-state. 

This lets us remove the re-training code from drivers and always go through the modeset path. At least for the DP drivers I've had experience with, this will make things simpler.

In addition to DP, I think we could also use the BAD link for HDCP failures in the future.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot